Landing Pages vs Content Hubs for AI

#01Why do many landing pages fail in AI search?

Our view: campaign landing pages are designed to convert paid traffic: a headline, a slogan, logos and a form. They're often noindexed, built in page builders that rely on script, or duplicated per campaign. That's fine for ads, but such pages give engines little to retrieve and nothing specific to quote.

#02Which landing pages should be indexable?

Our view: for ad variants that duplicate a core page, use canonical tags or noindex, and invest in the core page instead (Google).

#03What text should an indexable landing page include?

• A 40–60 word answer: what it is, who it's for, the outcome
• Three to six question sections on the main concerns
• Specific proof: customers, measured results, certifications
• A short FAQ with genuinely different questions
• Links to deeper pages, docs and pricing

Google recommends ensuring important content is available in text and that JavaScript-generated content can be rendered (Google).

#04What is a content hub?

A hub page summarises a topic and links to spoke pages that cover subtopics in depth, each linking back.

Our view: a hub makes your coverage easy to navigate and tells crawlers which pages belong together. It's a structure, not a trick.

#05How do you build a hub?

1. Choose a topic where you have several genuine subtopics.
2. Write the hub with a direct answer and a short summary per subtopic.
3. Create or consolidate spoke pages, one per subtopic.
4. Link spoke ↔ hub and spoke ↔ related spoke with descriptive anchor text.
5. Add breadcrumbs.
6. Review hub and spokes together on a schedule.

#06How do you write internal links?

Google recommends descriptive anchor text that tells users and Google about the linked page (Google). Our view: "holiday pay calculations for part-time staff" is better than "click here" or "learn more".

#07How do you avoid thin variants?

Our view: before creating a page, ask whether it would answer a different need from existing pages. "Invoice software for builders" and "invoice software for construction firms" are the same need; one page is enough. Merge existing near-duplicates with redirects (Google).

#08What's a worked example?

Fictional example: an HR software company has 40 campaign landing pages, mostly noindexed, plus scattered blog posts on onboarding. It builds an "Employee onboarding" hub with a direct answer, sections for checklists, legal paperwork by country, remote onboarding and software, each linking to a spoke page. It merges six overlapping blog posts into spokes with redirects, makes its core onboarding product page indexable with real text, and keeps ad variants canonicalised to it.

#09How do you measure hubs?

• Search Console performance for hub and spokes (Google)
• Prompt tests for the topic and subtopics
• Internal click-through from hub to spokes

#10Which pitfalls should you watch for?

• Hubs that are just link lists with no content
• Dozens of near-identical landing pages
• Product pages built entirely in script
• Hubs that never get updated
• Orphan spokes with no links back

#11How do landing pages and hubs work together?

Our view: the hub informs, the landing page converts. Link from the hub's product section to the core landing page, and from the landing page to the hub for readers who want to learn more first. Keep the facts identical in both, ideally from a shared source, so neither drifts out of date.

#12How big should a hub be?

Our view: as big as the topic's genuine subtopics, often five to fifteen spokes. If a hub has fifty spokes, consider splitting it into several hubs. If it has two, it may just be one good guide.

#13Are your hub links crawlable?

Google says it can generally only crawl links that are <a> elements with an href attribute; most other link formats won't be parsed (Google). Our view: check that hub navigation built with buttons or script click handlers also uses real links, or spokes may not be discovered.

#14Checklist

• Core landing pages indexable with real text
• Ad variants canonicalised or noindexed
• Hub with direct answer and summaries
• One spoke per distinct subtopic
• Descriptive two-way links
• Near-duplicates merged

#15From MentionX data: which page types get citedOriginal data

Method. Read-only aggregate queries over MentionX scans from 22 August to 29 October 2026 (UTC): 2,217 engine runs (2,154 completed) across 18 anonymised projects and six engines.

In the MentionX sample, cited URLs spread across page types:

Our view: blog and article pages, the building blocks of hubs, make up the largest share here. Homepages and pricing pages also appear, so landing pages with real substance can be cited too.

Limits. A convenience sample of mostly B2B software projects, run through engine APIs, which can behave differently from the consumer apps. Perplexity, Copilot and DeepSeek figures come from a single day (26 October 2026), so treat them as a snapshot, not a trend.

#16Worked example: Ledgerline builds an invoice-approval hub

Ledgerline is a fictional accounts-payable tool. Figures are illustrative.

Ledgerline has a dozen thin campaign landing pages for invoice approval. The team keeps the two strongest indexable and adds a clear explanation, a feature table and FAQs to each. The rest get a noindex tag.

It then builds a hub: an overview page on invoice approval linking to eight guides on approval limits, three-way matching, audit trails and more. Each guide links back to the overview and to the relevant landing page. After a quarter, the hub's guides start appearing as citations in a few problem prompts in this illustrative example.

#17How do you decide what belongs in a hub?

List the questions buyers ask about the topic, group them, and write one page per question or group. The hub overview should introduce the topic and link to every page.

#18How do you keep a hub up to date?

Review it quarterly. Update pages with new information, merge overlapping ones and add pages for new questions. Note the last-updated date on each page.

#19Should landing pages have FAQs?

Yes, if they answer real questions buyers ask. Keep answers short and accurate.

#20What should the hub overview page say?

The overview should define the topic in plain language, explain who it matters to and summarise the main questions, each linking to its own guide. A short paragraph per subtopic works well. It should be useful on its own, so a reader who only sees the overview still learns the basics. Our view: a hub overview that's just a list of links gives engines nothing to quote.

#21How do you structure a strong landing page?

Open with what the product does and who it's for in one or two sentences. Follow with the main benefits, each explained with a concrete example. Add a feature table, pricing or a link to it, integrations, proof such as case studies or reviews, and FAQs. Keep the call to action clear, but let the text do the explaining.

#22When should a landing page become a hub page?

When the topic needs more explanation than one page can hold, or when buyers ask many related questions. A landing page for invoice approval might link to a hub of guides on approval workflows. The landing page converts; the hub educates. Keep both and link them.

#23How do you handle paid campaign pages?

Paid campaign pages are often near-duplicates with small changes for each ad group. Keep them out of the index with noindex, so they don't compete with your main pages or dilute what engines read. Use canonical tags if variants must stay crawlable.

#24How do you prevent hubs from cannibalising each other?

Give each page a distinct question to answer. If two pages answer the same question, merge them and redirect the weaker one. Check your hub list against search and prompt data to spot overlap.

#25How do you measure whether landing pages are read by engines?

Check server logs for AI crawler visits to landing pages, then run brand-specific and decision prompts to see whether engines describe the product accurately. If answers cite third-party pages instead of yours, compare what those pages say that yours don't. Often the difference is a clear statement of what the product does, for whom and at what price. Our view: landing pages that answer those three questions plainly are far more useful to engines than pages built around a slogan.

#26How do you plan a hub rollout?

Publish the overview and the three most important guides first, then add the rest over a few weeks. Link each new guide from the overview as it goes live. Review internal links at the end to make sure every page links back to the overview and to at least one related guide.

#27What should you do first?

List your indexable landing pages, mark the thin ones and decide for each whether to improve it or noindex it. Then pick one topic for your first hub.

#28Common questions

Should every landing page be indexed? No. Index pages with substantial, unique content; noindex thin variants.

How many pages should a hub have? Enough to cover the topic's key questions; often five to fifteen.

Do hubs help AI visibility? They can, by giving engines clear, linked explanations to cite.

Should hubs link to landing pages? Yes, where it helps readers take the next step.

#29Related

• Creating definitive guides that earn citations
• Programmatic SEO in the AI era