Search Marketing FAQ

E-commerce pattern: each product = page in programmatic catalog. Variations: by attribute (color/size), by use case, by audience. Examples: Etsy product pages, Amazon product pages. Programmatic challenge: thin content if descriptions are copied from manufacturer. Solution: original product descriptions, customer reviews, Q&A, related-product comparisons, schema markup, unique imagery.

in Programmatic SEO

Five categories. Etsy product listings (millions of seller products). Amazon product pages. Capterra software listings ('Project Management Software'). G2 software comparisons. Houzz product database. Each scales product pages with unique descriptions + reviews + categories + comparisons. Marketplaces own the pSEO product pattern; brand-direct sites can apply similar tactics to their own catalogs.

in Programmatic SEO

Pattern: [Product A] vs [Product B]. Examples: NerdWallet credit card comparisons, G2 software comparisons. Template renders side-by-side comparison of features, pricing, ratings, pros/cons. Data per page: two products + comparison framework. Often paired with category pages (best of [category]). Comparison content captures high-intent buyers in decision stage. Strong programmatic pattern for SaaS, financial products, tools.

in Programmatic SEO

Pattern: [Question] about [Topic]. Examples: each question + answer pair becomes its own page targeting long-tail informational queries. Aggregated from PAA boxes, customer questions, industry FAQs. Template: H1 = question, H2 sections = answer + context + related questions + related products. Marketing companies use this pattern for thought leadership; SaaS for help center SEO. FAQPage schema markup enabled.

in Programmatic SEO

Five-element internal linking. Hub pages (category landing pages linking out to programmatic pages). Sibling links (related programmatic pages link to each other). Breadcrumbs (Category > Subcategory > Page). Footer category links (sitewide). Contextual links within content. Goal: each programmatic page has 5-20 inbound internal links. Hub-and-spoke structure helps search engines crawl + signal hierarchy.

in Programmatic SEO

Match schema type to page content. Location pages → LocalBusiness or Place. Product pages → Product. Comparison pages → Article. FAQ pages → FAQPage. Generate schema dynamically from same data feed that generates content. Validate sample pages with Rich Results Test. Schema markup helps each programmatic page be recognized as distinct entity, not just template variation.

in Programmatic SEO

Five tooling categories. Custom-built (Next.js with database integration - most powerful). Webflow + Whalesync (mid-market). Webflow + Make.com (no-code automation). Notion + custom static-site generator. Specialty pSEO platforms (Wordpress with custom plugins, Bubble). Choice depends on scale (50 pages vs 50,000 pages) + technical resources + budget. Most pSEO at scale uses custom or Next.js implementations.

in Programmatic SEO

Five tactics. Internal link structure (hub pages link to programmatic pages efficiently). XML sitemap chunked by category (50,000 URLs per sitemap). Noindex low-value variations. Server-side rendering (faster crawl). Reasonable URL depth (max 3-4 levels). Crawl budget matters at 100,000+ pages. Below that, most sites don't have crawl budget concerns. Monitor GSC crawl stats.

in Programmatic SEO

Five-step maintenance. Monthly indexation check (GSC Coverage report). Quarterly thin-content audit (pages with low traffic + low engagement). Data feed health monitoring (entities updating? new entities added?). Template improvements (A/B test variations). Prune dead pages (entities no longer exist). Programmatic SEO is operational - requires ongoing maintenance, not set-and-forget.

in Programmatic SEO

Eight common mistakes. Thin content per page (only template + name). Massive launch (50,000 pages at once). No demand validation. Duplicate content from poor template design. Generic schema markup. Poor internal linking. Ignoring crawl budget at scale. No maintenance after launch. Most failures are quality control issues, not technical implementation issues. Prioritize template + data quality over scale.

in Programmatic SEO

Controls bot access to URLs. Blocks crawling of low-value/internal pages (admin, search, cart), conserves crawl budget on large sites, manages AI bot access. Located at root: yoursite.com/robots.txt. Critical for: large sites (crawl budget), e-commerce (filter URLs), AI bot management. Misconfigured robots.txt is one of the most common 'why isn't my site ranking' culprits.

in Technical SEO: Crawl & Index

Allow: all public-facing content (pages, products, blog posts). Block: admin areas, search result pages, internal tools, duplicate URLs, faceted-navigation parameter URLs. Don't block: actual content pages you want indexed. Don't try to use robots.txt to remove indexed content (use noindex instead - robots.txt prevents crawling, not indexing of already-indexed URLs).

in Technical SEO: Crawl & Index

No - robots.txt prevents crawling. If a page is linked from somewhere Google sees, it may still appear in search results (as URL-only result) even when blocked. To prevent indexing: use noindex meta tag (requires Google to crawl the page) or HTTP X-Robots-Tag noindex header. Many SEOs misuse robots.txt for de-indexation - it doesn't work.

in Technical SEO: Crawl & Index

Three tools. Google Search Console robots.txt tester (Settings → Crawl). Online validators (TechnicalSEO.com robots.txt tester). Curl simulation: 'curl -A "Googlebot" https://yoursite.com/robots.txt'. Test specific URLs to confirm allow/disallow behavior. Audit robots.txt monthly - changes can have huge impact. Misconfigured robots.txt has caused many SEO disasters.

in Technical SEO: Crawl & Index

Six common mistakes. Blocking entire site with 'Disallow: /' (typo or test-environment leak). Blocking CSS/JS (prevents proper rendering). Blocking sitemap.xml (Google can't discover URLs). Forgetting to allow Googlebot specifically. Using robots.txt to try to de-index already-indexed pages. Using complex regex Google doesn't fully support. Test thoroughly before deploying changes.

in Technical SEO: Crawl & Index

Structured file listing all URLs you want indexed. Submitted to Google Search Console (and other search engines). Helps Googlebot discover URLs faster, especially on large sites or sites with poor internal linking. Includes: URL, last-modified date, change frequency, priority. Required for: large sites (>10,000 URLs), new sites, sites with deep architecture. Generated automatically by most CMSes.

in Technical SEO: Crawl & Index

Maximum 50,000 URLs per sitemap (Google limit). 50MB uncompressed file size limit. For larger sites, use multiple sitemaps + sitemap index file. Group sitemaps logically (products sitemap, blog sitemap, pages sitemap) for easier debugging. Submit sitemap index in GSC. Most sites under 50K URLs need one sitemap; large e-commerce needs sitemap index.

in Technical SEO: Crawl & Index

No. Sitemap should contain only canonical, indexable URLs (200 status, no noindex, no canonical pointing elsewhere). Including noindex or redirected URLs confuses Google + wastes crawl budget. Audit sitemap quarterly: should be 100% canonical indexable URLs. Most CMS auto-generated sitemaps include junk - manually filter or use SEO plugin with proper rules.

in Technical SEO: Crawl & Index

HTML tag declaring the canonical (primary) URL for a piece of content. Syntax: <link rel='canonical' href='https://example.com/canonical-url'>. Use when: multiple URLs serve similar/identical content (tracking parameters, sort/filter variations, duplicate listings), pagination, syndicated content, mobile vs desktop URLs. Self-canonicalize indexable pages. Skipping canonicals causes duplicate content issues.

in Technical SEO: Crawl & Index

Three mechanisms. Tell Google which URL is the 'real' version when multiple URLs serve similar content. Consolidate ranking signals from duplicates to the canonical URL. Prevent dilution across multiple URLs competing for same query. Without canonicals, Google picks one but may pick wrong one. With canonicals, you control which URL ranks. Critical for e-commerce with filter URLs.

in Technical SEO: Crawl & Index

Six common errors. Canonical pointing to noindex page (signals conflict). Canonical pointing to 404 or redirected page. Multiple canonical tags on one page. Self-referential canonical inconsistencies (canonical to URL different from current page URL). Canonical to URL on different domain (intentional for syndicated content; mistake elsewhere). Test canonicals during content audits.

in Technical SEO: Crawl & Index

Three-step process. Identify via ScreamingFrog 'Response Codes → Redirection (3xx)' tab. Update internal links pointing to first URL → direct to final URL. Update external links if possible (request webmaster updates). Chains of 3+ redirects significantly hurt page speed + crawl budget. Direct redirects (one hop) are fine. Chain hops compound load time.

in Technical SEO: Crawl & Index

Six tactics. Block crawl of low-value URLs (filter parameters, internal search) in robots.txt. Reduce redirect chains. Eliminate duplicate URLs via canonicals. Maintain fast server response time (faster = more pages crawled per visit). Submit clean XML sitemap. Monitor crawl stats in GSC. Crawl budget matters at 100,000+ URLs. Below that, most sites don't have budget constraints.

in Technical SEO: Crawl & Index

Optimizing JavaScript-rendered content for search engines. Modern frameworks (React, Vue, Angular) render content client-side - bots must execute JavaScript to see the page. JavaScript SEO ensures: bots can render content, indexable HTML is present, critical content not delayed by JS execution. Required when site uses SPA architecture. Static HTML sites don't have JS SEO concerns.

in JavaScript SEO & Log Analysis