Review workflow
The review process starts with the decision a user is trying to make: accept, negotiate, relocate, compare cities, compare compensation components, or reject a fragile offer. A page is useful only if it helps that decision with visible assumptions.
Generated pages are checked for title, meta description, canonical URL, FAQ schema, article schema, sitemap inclusion, internal links, and enough body content to answer the intent. Pages that only repeat a keyword without explaining the decision should be expanded or removed.
Quality gates
OfferScope pages should pass basic static checks before deployment. JavaScript should parse. JSON-LD blocks should be valid JSON. Homepage links should resolve locally. The sitemap should contain unique URLs. Generated pages should include a clear disclaimer path through the footer or trust pages.
Localization should be checked with representative languages from different scripts, including Chinese, Japanese, Arabic, and a Latin-script language. The goal is not only page count; the goal is a crawlable, understandable path for each language.
| Gate | Evidence | Why it matters |
|---|---|---|
| Generator syntax | node --check tools/*.mjs | Prevents broken page generation. |
| JSON-LD validity | Parse sampled schema blocks | Protects search enhancements. |
| Internal links | Resolve homepage local hrefs | Prevents dead SEO paths. |
| Sitemap uniqueness | Count loc values and unique set | Avoids duplicate crawl waste. |
| GA4 ID | analytics.js contains the production measurement ID | Preserves traffic measurement after deployment. |
Keyword review
Keyword review should combine calculator-intent phrases, relocation and remote-work phrases, city and country modifiers, role-specific modifiers, and trust queries about methodology or data sources. Search terms should be mapped to the most useful page type instead of forcing every keyword onto the homepage.
The keyword map in data/seo-keywords.json is the working backlog. It should be updated when new long-tail patterns appear in Search Console, public forums, or competitor pages.
Deployment review
After a major update, deployment should happen from the terminal using the project’s current deployment path. The deploy step should not be considered complete until the command succeeds and the deployed artifact contains the updated analytics ID, sitemap, and generated pages.
FAQ
What counts as a major OfferScope update? A major update changes page inventory, sitemap coverage, trust content, analytics, or deployment output.
Why inspect generated pages instead of only the source generator? The deployed site serves HTML files, so generated output is the final evidence for crawlers and users.
How often should the keyword map be refreshed? Monthly is a practical baseline, with faster refreshes after Search Console reveals new high-intent queries.