Should you keep or remove old FAQ pages during a redesign?

Decide an old FAQ’s future through the remaining need, answer accuracy and available replacement. Examine known links and uses too. Keeping, revising, merging and retiring are distinct decisions, each requiring URL and internal-link handling suited to the content.

Why FAQ pages still matter in a redesign

Old FAQ pages often carry more value than teams expect. They can rank for long-tail questions, capture pre-sales intent, reduce support friction, and strengthen internal linking to service pages. For redesign projects, this matters because deleting question-based URLs without evidence often removes the exact content layer that helps users compare options, clarify objections, and convert later in the journey. Google’s guidance continues to prioritise helpful, reliable, people-first content rather than content built only for search features. developers.google.com

They also matter beyond classic SEO. Good FAQ content can support SXO by reducing hesitation, AEO by giving concise answer formats, and LLM visibility by exposing clear, scannable question-answer pairs that models can more easily interpret. Google’s documentation on AI features says the same foundational search practices still apply: technical accessibility, policy compliance, visible content alignment, and useful information. developers.google.com

When keeping an old FAQ page is the right choice

• The page answers a recurring customer question that sales or support teams still receive.
• The URL earns organic traffic or impressions, especially on long-tail queries.
• The page attracts backlinks or is cited in documentation, emails, or external resources.
• The content supports conversion by resolving objections on pricing, process, delivery, compliance, timing, or scope.
• The page fills an intent gap not covered well by category, service, or product pages.
• The local variant matters, for example questions about service areas, implementation conditions, or regional constraints.

When removal or consolidation is the better option

• The answers are outdated after product, pricing, policy, or service changes.
• Several FAQ pages target the same question and compete with each other.
• The page is thin, with shallow answers that add no unique value.
• The FAQ exists only for search footprint and has no clear audience.
• The page conflicts with current commercial pages and sends mixed messages.
• The content belongs inside a stronger destination, such as a service page, local page, knowledge base article, or case-study hub.

The audit method to use before deciding

1. Inventory all FAQ URLs. Include live pages, orphan pages, paginated archives, tag-based FAQ sections, and hidden URLs that still receive traffic.
2. Pull performance data. Review clicks, impressions, ranking queries, assisted conversions, engagement, internal search demand, and support-ticket themes.
3. Check authority signals. Look for backlinks, internal links, external mentions, and pages that other teams still use.
4. Score content quality. Is the answer accurate, complete, current, specific, and better than what a service page already says?
5. Map each page to a primary intent. Informational, commercial investigation, transactional support, post-sale support, or local intent.
6. Assign one action per URL. Keep, merge, rewrite, redirect, or remove with a justified status decision.

This is the same logic we apply in a structured website redesign process: content decisions should follow evidence, not aesthetics.

How to judge FAQ pages for SEO

For SEO, the main risk is not having FAQ pages. The risk is changing or deleting URLs that already hold relevance without preserving intent and equity. During redesigns, many traffic losses come from broken URL mapping, weaker replacement pages, or merged content that no longer targets the original question clearly.

Keep a page if it owns useful queries and still satisfies them. Merge it if another page can satisfy the same query better and more completely. Remove it only if no valuable search demand, link equity, or business usefulness remains. If you remove or merge, use clean redirects to the most relevant destination, not to the homepage.

Google Search stopped displaying FAQ rich results on 7 May 2026. Official Google Search updates. FAQPage remains descriptive vocabulary: keep useful answers without promising that display.

The checks to make before launch

1. No valuable FAQ URL is left without a mapped destination.
2. Redirects point to the closest intent match, not to generic pages.
3. Kept pages answer the query better than before, not just with new design.
4. FAQ sections are crawlable and visible in the rendered page.
5. Structured data matches the final on-page wording.
6. Core Web Vitals are not degraded by redesigned components. developers.google.com

The practical rule to apply

Keep old FAQ pages when they still earn trust, traffic, or conversion assistance. Remove them when they are obsolete, duplicative, or strategically empty. Merge them when the same intent can be satisfied better on a stronger page. In most redesigns, the winning move is not deletion; it is rationalisation.

If you are planning a redesign, the next step is simple: build a FAQ URL audit, score each page across search value and user value, and decide keep, merge, rewrite, or remove before any design templates are finalised. If you want that audit tied directly to the new site structure, start with a redesign review or contact our team.