Chapter 11: Technical setup across platforms
You’ve planned your hub, chosen your business-type architecture, and know how to write for AI citation. Now you need to actually build the thing on your website.
This chapter covers the technical implementation on the major CMS platforms, including the schema markup and site architecture details that make the difference between a hub that looks right and one that performs.
WordPress: the full-featured option
WordPress gives you the most control over every aspect of your blog hub.
Categories, tags, custom taxonomies, URL structures, internal linking plugins, and full schema markup support are all available out of the box or through well-maintained plugins.
For URL structure, use a pattern that reflects your hub architecture. Your pillar page should live at a clean URL like yoursite.com/blog/email-marketing-guide/.
Cluster pages should be at the same level: yoursite.com/blog/abandoned-cart-emails/, yoursite.com/blog/email-segmentation-shopify/.
Don’t nest cluster pages under the pillar URL (like yoursite.com/blog/email-marketing-guide/abandoned-cart-emails/) because flat URL structures perform better for both SEO and AI crawling.
Use WordPress categories to group hub content. Create a category for each hub topic (e.g., “Email Marketing”) and assign every hub page to that category.
This creates an additional taxonomy page that functions as an alternate index for your hub content, and AI crawlers can use it to discover related pages.
Two WordPress plugins make hub building significantly easier. Link Whisper scans your content for internal linking opportunities and suggests relevant links between related posts.
It saves hours of manual linking work. Yoast SEO (or Rank Math) handles schema markup, XML sitemaps, and basic on-page optimization.
Both are worth the investment if you’re building hubs on WordPress.
For the internal linking itself, add links manually in the body text rather than relying solely on “related posts” widgets. Automated widgets help but they don’t replace contextual body links.
Each cluster page should have 3-8 internal links: one to the pillar page within the first 200-300 words, 2-3 to related cluster pages, and any natural links to product or service pages.
Shopify: working around the limitations
Shopify is primarily an ecommerce platform, and its blog functionality reflects that.
The native Shopify blog works for basic posts, but it lacks several features that make hub building easier on WordPress: no custom taxonomies, limited URL structure control, no built-in internal linking tools, and restricted schema markup options without custom code or apps.
The best approach for Shopify is to use the native blog for your cluster content and use collection pages as your pillar pages.
This plays to Shopify’s strengths: collection pages are well-supported, easily customizable, and already linked from navigation menus.
Add introductory content to your collection page that provides hub overview value, then link to your cluster blog posts within that content.
For internal linking on Shopify, you’ll need to add links manually in the blog post editor. There’s no equivalent of Link Whisper for Shopify.
Some apps (like Linkbot) can help automate internal link suggestions, but manual placement in the body text remains the most effective approach.
If your hub needs are more complex than what Shopify’s native blog supports, consider a headless CMS approach: use Shopify for your storefront and checkout, and a separate CMS (Sanity, Contentful, or Ghost) for your blog content, connected through APIs.
This is a more technical setup that typically requires a developer, but it gives you full control over content architecture while keeping Shopify’s commerce capabilities.
Squarespace, Wix, and other platforms
Squarespace offers decent blogging with categories, tags, and clean URLs. You can build a basic hub on Squarespace by using blog categories for hub grouping and manual internal linking.
The limitations are less control over schema markup (limited to what Squarespace generates automatically) and no internal linking plugins.
For small hubs (5-10 cluster pages), Squarespace works fine. For larger hubs, WordPress is a better choice.
Wix has improved its SEO capabilities significantly, including built-in structured data, automatic sitemaps, and basic blogging.
Like Squarespace, it works for small hubs but becomes limiting at scale. Wix’s URL structure is less clean than WordPress or Squarespace, which can slightly affect crawlability.
For any platform, the non-negotiable requirements are: the ability to create blog posts with custom URLs, the ability to add internal links within body text, the ability to set up basic meta tags (title, description), and the ability to organize content by category or tag.
If your platform can do these four things, you can build a functional hub.
Schema markup and the three-click rule
Schema markup helps AI engines understand what your page is about at a structural level. For hub pages, three schema types are most relevant.
Article schema tells the AI engine that your page is an article, who wrote it, when it was published, and when it was last updated.
This is the bare minimum for every cluster page. FAQPage schema wraps question-and-answer content in a structured format that AI engines can extract directly.
If your cluster page answers specific questions (and it should), add FAQPage schema for the main Q&A pairs.
BreadcrumbList schema shows the AI engine where your page sits in the site hierarchy, which reinforces the hub structure.
On WordPress, Yoast and Rank Math handle Article and BreadcrumbList schema automatically. FAQPage schema can be added through Yoast’s FAQ block or through a dedicated schema plugin.
On Shopify, you’ll need to add schema through your theme’s code or use an app like JSON-LD for SEO.
On Squarespace and Wix, schema options are more limited; use their built-in structured data features and supplement with custom code where possible.
The three-click rule is a site architecture principle that affects hub performance.
Pages within three clicks of the homepage generate roughly nine times more traffic than pages buried deeper, per My Ranking Metrics’ research.
For your hub, this means your pillar page should be linked from your main navigation or homepage (one click). Cluster pages should be linked from the pillar page (two clicks).
If any cluster page requires four or more clicks to reach from the homepage, restructure your navigation to bring it closer.
| Platform | URL control | Schema support | Linking plugins | Hub suitability | ||
| WordPress | Full | Full (via plugins) | Yes (Link Whisper, Yoast) | Best for complex, large-scale hubs | ||
| Shopify | Moderate | Requires apps/code | Limited (Linkbot) | Good for ecommerce hubs with collection-as-pillar | ||
| Squarespace | Good | Automatic (limited) | None | Fine for small hubs (5-10 pages) | ||
| Wix | Moderate | Built-in (basic) | None | Fine for small hubs with manual effort | ||
| Webflow | Full | Custom code | None | Flexible but requires technical setup | ||
| Prompt: Audit your hub’s click depth
Ask ChatGPT: “Here is my website’s navigation structure: [describe your menu items and blog layout]. My hub pillar page is at [URL]. My cluster pages are at [list URLs]. How many clicks does it take to reach each cluster page from the homepage? Which pages are buried too deep, and how should I restructure my navigation to bring everything within 3 clicks?” This identifies structural problems before they hurt your hub’s performance. |
||||||
