Internal Linking for Bricks Sites: Complete Guide
Bricks Builder is a modern, performance-focused WordPress page builder with powerful dynamic data capabilities. Here's how to implement effective internal linking that leverages Bricks' unique architecture and advanced features.
Understanding Bricks Builder's Modern Architecture
Bricks is a relatively new WordPress page builder (launched 2021) that has quickly gained traction among developers and performance-conscious users. Unlike Elementor, Divi, or WPBakery, Bricks generates clean HTML/CSS without shortcodes or excessive divs. It stores page structure as JSON in post metadata, similar to Elementor but with a more efficient data model. Bricks excels at dynamic content - pulling data from custom fields, taxonomies, and WooCommerce - making it popular for complex sites with custom post types and data-driven designs. For internal linking, this means you need tools that can parse Bricks' JSON metadata, understand dynamic content sources, and work with Bricks' template system (global elements, template parts, and reusable sections).
Internal Linking Challenges on Bricks Sites
JSON Metadata Storage
Bricks stores page structure as JSON in post metadata (_bricks_page_content_2), not in the standard post_content field. This means linking plugins that only read post_content will see nothing - your entire page is invisible to them. Tools need to specifically parse Bricks' JSON metadata to access element settings and extract text content from Rich Text elements, Headings, and other content-bearing elements.
Dynamic Data and Query Loops
Bricks' strength is dynamic content - a page might display ACF fields, WooCommerce product data, or custom post type information using dynamic tags. Internal links added to dynamic elements need to work correctly regardless of which specific post data is being displayed. A template showing product information should link appropriately for all products, not just one.
Template System and Global Elements
Bricks uses a sophisticated template system - templates for headers, footers, single posts, archives, and more. Global elements sync across pages. Adding internal links to templates means those links appear everywhere the template is used. You need to ensure template links are universally relevant, and use conditional logic if links should only appear for certain post types or conditions.
Element-Based Content Structure
Like other builders, Bricks divides content into elements - Rich Text, Heading, Text, List, and more. Content is fragmented across these elements, making it harder for automated tools to understand the full semantic context of a page. A complete discussion might span multiple Rich Text elements separated by Image, Video, or Divider elements.
Performance-Focused Clean Code
Bricks generates exceptionally clean HTML compared to other builders, which is great for performance but means there are fewer redundant content markers for linking tools to parse. The JSON structure needs to be interpreted correctly to understand not just the content but also the visual hierarchy and context that Bricks renders on the frontend.
Step-by-Step Guide
Install the WPLink Helper Plugin and Crawl Your Site
Bricks stores all page content in a custom database field (_bricks_page_content_2) that the standard WordPress REST API does not expose. To give WPLink access, first install the free WPLink Helper plugin from WordPress.org (search "WPLink AI Internal Linking" in Plugins > Add New). Once active, run a crawl in WPLink - it reads your Bricks content through the Helper plugin and builds a full inventory with accurate word counts, current links, and element breakdowns.
- •The Helper plugin takes about 2 minutes to install and requires no configuration beyond activation
- •Identify pages using Bricks templates or global elements so you can plan link placement carefully
- •Flag cornerstone pages and WooCommerce products that should receive more internal links
Design Hub-and-Spoke Content Clusters
Map your content into topical clusters. Bricks excels at creating sophisticated hub pages using Containers, Query Loops, and dynamic data. Build pillar pages for each major topic, showcasing related spoke pages with clear links. Use Bricks' Query Loop element to automatically display posts from specific categories or custom post types with links. Add manual links using Button elements and Rich Text for curated selections. Ensure all spoke pages link back to their hub to strengthen your site architecture.
- •Use Query Loop with Post Title and Post Excerpt elements to create dynamic hub pages linking to category posts
- •Create saved structures for 'Related Resources' sections with 3 Containers and Button elements
- •Design consistent button styles (Bricks global classes) for important internal links across your site
Add Contextual Links in Rich Text Elements
The primary location for contextual internal links in Bricks is the Rich Text element (and the older Text element, though Rich Text is preferred). Edit the element, click into the content editor, highlight anchor text, and add the link. Bricks' link interface lets you search for posts by title or enter custom URLs. Aim for 2-3 contextual links per long Rich Text element (400+ words), placed where they genuinely help readers explore related topics.
- •Use Bricks' link search to find target posts by title rather than copying URLs manually
- •Add links to List elements for clean, scannable lists of related resources
- •Leverage dynamic tags if you need links that change based on the current post (e.g., link to current category archive)
Leverage Button and Card Elements for Strategic Links
Beyond inline contextual links, use Bricks' Button element for clear CTAs and Card element for visually rich linked content blocks. Add buttons at the end of posts linking to cornerstone content, conversion pages, or next steps. Use the Posts element (query loop) to automatically link to related content by category or tag. Create custom Cards with background images, headings, and linked buttons for prominent internal navigation.
- •Create saved structures with 3 Button elements linking to your top cornerstone pages
- •Use Card elements with 'link entire card' option for large clickable internal navigation blocks
- •Add a Posts element at the bottom of blog posts, filtered by category, for automatic related links
Handle Templates and Global Elements Carefully
Before adding internal links to a Bricks template (header, footer, single post template, etc.) or global element, check where it appears across your site. Templates and global elements are perfect for sitewide navigation - a header menu, footer sitemap, or 'Popular Resources' section that is relevant everywhere. But do not add page-specific contextual links to templates. For page-specific links, use regular elements on individual pages, not global or template elements. Use Bricks' conditional logic if a template link should only appear for certain post types.
- •Use Bricks' 'Template conditions' to see where each template applies before adding links
- •Create post-type-specific templates ('Single Service' vs. 'Single Blog Post') with appropriate internal links for each
- •Use Bricks' 'Hide on conditions' feature to show certain internal links only on relevant pages
Monitor Performance and Iterate Your Link Structure
After implementing your internal linking strategy, track results using Google Search Console (internal link reports, indexed pages) and Google Analytics (page-to-page traffic flow). Verify that Bricks renders your links correctly on the frontend - check that dynamic links populate correctly and that links work on mobile. Use a crawler like Screaming Frog to ensure all links are discoverable. As you publish new content, revisit older pages to add links to new material.
- •Set up GA4 events to track clicks on Button element links to key conversion pages
- •Use Google Search Console's 'Links' report to confirm your hub pages are accumulating internal links
- •Re-crawl your site monthly with WPLink to discover new linking opportunities as your Bricks content grows
How WPLink Works with Bricks
WPLink supports Bricks Builder natively via the free WPLink Helper plugin (available on WordPress.org). Once the Helper plugin is installed on your site, WPLink reads the _bricks_page_content_2 JSON field to extract content from all element types - Rich Text, Heading, Text, List, Card, and more. It understands Bricks' element hierarchy for accurate semantic analysis. When you approve a link suggestion, WPLink writes the link directly into the Bricks JSON through the Helper plugin, preserving all element settings and styles.
Alternative Approaches
Link Whisper
- + Works directly in WordPress admin panel
- + Provides link suggestions as you write
- + Includes orphan content detection and link analytics
- - Cannot parse Bricks JSON metadata - completely misses Bricks-built content
- - Keyword-based suggestions miss semantic relationships
- - Annual subscription pricing instead of one-time license
Frequently Asked Questions
Related Articles
Ready to optimize your internal links?
Get started with WPLink today and see the difference.
Download WPLink