Should I use redirect traffic to auto-generate matching answer pages?

Generally, no. Using redirect traffic to dynamically auto-generate matching answer pages is usually a bad idea, especially if the pages are thin, low-quality, or created mainly to catch mismatched traffic. That can create search-quality and trust risks if the implementation is misleading or looks like it is made primarily to manipulate traffic matching.

Why this usually fails

1. Search quality risk: If pages are generated mainly to intercept redirected traffic rather than to answer a real user need, they may be viewed as low-value or manipulative.
2. Poor user experience: Auto-generated pages often feel generic or irrelevant, which can hurt trust and conversions.
3. Operational complexity: Building and maintaining redirect-based page generation adds technical overhead and can create performance issues.

Safer alternatives

• Programmatic SEO: Pre-build useful, indexable pages based on real search intent and structured data.
• PPC landing-page customization: Dynamic text replacement can be acceptable for paid landing pages when the page remains genuinely useful; if you want to avoid organic indexing, block indexing rather than relying on the page to carry SEO value.
• Straight redirects for site changes: For expired domains, merges, or removed pages, redirect to the closest relevant existing page, not to a fake auto-generated match.

Practical rule of thumb

If the page would not be useful on its own without the redirect, or if it exists mainly to game traffic matching, don’t do it.

One caveat: exact search-engine treatment can vary by implementation and context, so if this is for a live site, it’s worth checking the relevant search engine’s current guidelines.