SEO: rewrite page-1 zero-click snippets + overlay comparison article + FAQ schema#57
Open
philip638 wants to merge 1 commit into
Open
Conversation
… schema Targets the GSC finding that page-1 blog posts earn impressions but ~0 clicks (snippet problem, not ranking) and that VPN-comparison queries (nebula vs tailscale, etc.) rank page-1 with no dedicated page. Snippet rewrites (title/description) on 8 page-1 / near-page-1 posts that were ranking pos 7-13 with near-zero CTR. Outcome-led titles + descriptions that restate the query intent and promise a deliverable. blogPosts.ts titles synced so listing/related cards match each article H1. New article: pilot-vs-tailscale-nebula-zerotier-ai-agents — fair, accurate architecture comparison + decision guide. Captures the nebula/tailscale/ zerotier comparison cluster (120+ impressions, page-1, 0 clicks today). Includes a comparison table and an FAQ block answering the GEO-style queries. BlogLayout: new optional `faqItems` prop renders a visible FAQ section plus FAQPage JSON-LD (for AI Overviews). No change to posts that don't pass it. Note for reviewer: the .html duplicate URLs flagged in the GSC report already 308-redirect to clean URLs at the edge, so no redirect config was added — Google will consolidate on recrawl. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
From the latest GSC export (3-mo window): page-1 blog posts are pulling impressions but ~0 clicks — a snippet/CTR problem, not a ranking problem. Separately, VPN-comparison queries (
nebula vs tailscale,tailscale vs nebula,headscale vs nebula,zerotier vs tailscale) rank page-1 with 0 clicks and no dedicated page (~120+ combined impressions).This is the first "fix-the-leaks" batch: highest leverage, lowest risk.
What's in here
1. Snippet rewrites (8 posts, pos ~7–13, near-zero CTR) — outcome-led
<title>+<meta description>that restate the query intent and promise a deliverable (code/guide). Page meta comes from each post'sBlogLayoutprops;blogPosts.tstitles synced so listing/related cards match each article's H1 (kept the existing stat-driven card descriptions).2. New article —
pilot-vs-tailscale-nebula-zerotier-ai-agents. Fair, accurate architecture comparison + decision guide (comparison table, "which should you choose", honest "Pilot isn't a VPN" framing). Targets the comparison cluster above. SVG banner committed so the card/OG image resolve (swap for a real banner anytime).3. FAQ schema capability —
BlogLayoutgains an optionalfaqItemsprop that renders a visible FAQ section andFAQPageJSON-LD (for AI Overviews). Posts that don't pass it are unchanged. Used by the new article; ready to roll out to the top-6 posts in a follow-up.Verification
npm run build✓ (191 pages) ·npm run check:plain✓ (no orphans)Note on the
.htmlduplicatesThe GSC report flagged
.htmlvs clean-URL cannibalization. Those URLs already 308-redirect to the clean path at the edge (verified live), so I did not add redirect config — Google will consolidate on recrawl. Flagging in case you'd prefer an explicit_redirectsrule anyway.🤖 Generated with Claude Code