Target tbc audit intent: metadata pass + dedicated landing page - #9
Merged
Conversation
Search Console shows two distinct query populations on the homepage: "analyzer" queries (~1.5k impressions) convert at 10-36%, while navigational "wow tbc logs"-style queries (~14k impressions, people looking for warcraftlogs.com) convert at ~0.2%. The site-wide CTR decline is that second group growing, not a regression — so this change ignores it and targets the one high-volume query with genuine tool intent instead. - Homepage title: add "Raid Audit". `tbc audit` is 3.3k impressions at position 4.9 with 0.61% CTR; the word was absent from the title, so searchers never saw their term matched. Keeps "Log Analyzer" intact — those queries are the 30%+ CTR group. Drops "Classic" to stay under SERP truncation; it remains in the description and H1. - Homepage description: lead with the paste-a-URL action and name the specific things audited. - Guide: retarget from the navigational cluster (91% of its impressions, unwinnable against warcraftlogs.com) toward the genuine-intent queries it already surfaces for. Description now matches the page's actual 7-step structure. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DzE8p4mzrJjXKSqMhj3YHN
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
`tbc audit` is our largest non-navigational query — ~3,280 impressions per 28d at position ~4.9, converting at 0.61%, with the general-purpose homepage as the only thing ranking for it. Unlike the "wow tbc logs" cluster (navigational, people looking for warcraftlogs.com), these searchers want an auditing tool, which is exactly what the Buff & Gear Audit tab is. That feature had no dedicated URL until now. This is a feature page, not a doorway: every check described is one the CLA engine actually runs, verified against lib/cla-engine.ts and lib/constants.ts — enchants and severity tiers (error/warning/info → CRITICAL/WARNING/NOTE), sockets, gem type, TBC weapon oils and sharpening stones, item level, flasks, battle/guardian elixirs, food, scrolls, class buff families incl. the Salvation-on-tank warning, and the 61-point TBC talent check. - New `/tbc-audit` with the URL form inline (matches tool intent), plus BreadcrumbList and FAQPage JSON-LD. - Linked from the homepage and added to the sitemap at priority 0.9. Prior experience here is that unlinked pages sit in "Discovered – currently not indexed", so the internal link is load-bearing. - Fixed a stale claim in ReportUrlForm: it said "Supports Classic and Season of Discovery reports" while the app has handled TBC through Cataclysm for a while (EXPANSION_ID_TO_DOMAIN, 1000-1004). It read as a direct contradiction on a TBC page. Verified: tsc + lint clean; page rendered locally and checked end to end (title 58 chars incl. the " | ParseForge" template, canonical, JSON-LD, and the crawlable homepage anchor). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DzE8p4mzrJjXKSqMhj3YHN
alexandermayes
changed the title
tbc audit intent: metadata pass + dedicated landing page
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
1 participant
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
Investigating a suspected click decline turned up the opposite: clicks are up (July 991 vs June 941; last 14d 495 vs prior 409), average position improved 6.6 → 6.2. What's falling is CTR — and it's a composition effect, not a regression.
The homepage serves two unrelated query populations:
tbc log analyzer,wow log analyzer)wow tbc logs,wow logs tbc,logs tbc)Group B is people trying to reach warcraftlogs.com. We rank ~5th, they don't click, and no title fixes that — its growth is the entire CTR decline. Both commits here ignore Group B and target the one high-volume query with real tool intent:
tbc audit, 3,280 impressions at position 4.9, 0.61% CTR.Commit 1 — metadata
app/layout.tsx— title →Free WoW TBC Log Analyzer & Raid Audit — ParseForge. "Audit" was missing entirely, so the term never bolded in the SERP. "Log Analyzer" is preserved deliberately: that's the 30%+ CTR group.app/guides/how-to-analyze-wow-classic-logs— 91% of this page's impressions are the navigationalclassic logscluster at ~0.1% CTR. Retargeted at the genuine-intent queries it already surfaces for, and the description now matches the page's actual 7-step structure.Commit 2 —
/tbc-auditlanding pageThe raid-wide Buff & Gear Audit already exists as a tab but had no dedicated URL, so the homepage was competing for
tbc auditalone.This is a feature page, not a doorway. Every check described is one the CLA engine actually runs, verified against
lib/cla-engine.tsandlib/constants.ts: enchants with the real severity tiers (error/warning/info→ CRITICAL/WARNING/NOTE), empty sockets, wrong gem type, TBC weapon oils and sharpening stones, item level, flasks, battle/guardian elixir pairing, food, scrolls, class buff families including the Salvation-on-tank threat warning, and the 61-point TBC talent check.Also fixed a stale claim in
ReportUrlForm: it said "Supports Classic and Season of Discovery reports" while the app has handled TBC through Cataclysm for a while (EXPANSION_ID_TO_DOMAIN, 1000–1004). On a TBC page that read as a direct contradiction.Tradeoff to review
The homepage title drops "Classic" to fit "Audit" under SERP truncation (51 chars). The data is heavily TBC-weighted —
wow classic log analyzeris 22 impressions against TBC terms dominating the top 20 — so I judged it worth it, and "Classic" stays in the description, H1, and the new page's FAQ. If you'd rather keep both:Free WoW Classic & TBC Log Analyzer + Raid Audit — ParseForgeis 61 chars and risks truncation.Verification
npx tsc --noEmitandnpm run lintclean. The new page was rendered locally and checked end to end: title 58 chars including the| ParseForgetemplate (an earlier draft was 70 and would have truncated — caught by rendering it), canonical, both JSON-LD blocks, and the crawlable server-rendered homepage anchor. Visually confirmed against the site's existing styling.No SEO invariants touched — canonicals, indexability rules, and
recordRecentReport/getRecentReportsare unchanged.Expected impact
Modest and deliberately so:
tbc auditmoving 0.61% → ~1.5–2% is roughly +30–50 clicks/month from the metadata alone. The landing page is the larger and slower bet — it needs to index and earn its own ranking before it contributes, so judge it on a 4–8 week horizon, and track thetbc auditquery specifically rather than site-wide CTR, which Group B's growth will keep dragging down regardless.🤖 Generated with Claude Code
https://claude.ai/code/session_01DzE8p4mzrJjXKSqMhj3YHN