Editorial operations

Content Operations Playbook

A controlled workflow for growing the Google SEO content matrix without weakening compliance, duplicating search intent, or losing internal-link discipline.

5 workflows15 steps

Keyword and User Research

Turn search data and user questions into a controlled editorial queue.

3 steps

Collect GSC query opportunities

Review queries with impressions, low CTR, or missing dedicated pages in Google Search Console.

Output: Keyword brief

Map keyword intent to page type

Classify each opportunity as calculator landing page, glossary term, state page, tax interaction, blog guide, or operations page.

Output: Keyword brief

Prioritize professional-review topics

Flag tax-sensitive topics such as penalties, basis, RMDs, IRMAA, and tax credits for additional review.

Output: Editorial queue

Content Production

Create useful pages that support the calculator without making personal recommendations.

3 steps

Draft educational copy

Write plain-English explanations, assumptions, model limits, and calculator entry paths.

Output: Draft page

Add internal links to calculator

Link users back to /#calculator and relevant methodology, glossary, or tax-reference pages.

Output: Internal link checklist

Add metadata and structured data

Set title, description, canonical path, breadcrumbs, and applicable Article or DefinedTerm data.

Output: SEO checklist

Editorial and Compliance Review

Protect trust and avoid drifting into tax, financial, legal, or investment advice.

3 steps

Run compliance copy review

Remove should/should not recommendations, guarantees, filing instructions, and personalized tax conclusions.

Output: Compliance review

Verify disclaimer placement

Confirm the required educational disclaimer appears on calculator-adjacent and tax-sensitive pages.

Output: Compliance review

Check source freshness

Confirm tax-year references, IRS source links, and methodology assumptions match the current release.

Output: Source note

Publishing and Discovery

Ship new pages through the same discoverability and rollback systems as product features.

3 steps

Add sitemap coverage

Ensure new pages are included in sitemap generation and reachable from at least one hub.

Output: Sitemap diff

Update site index and llms.txt when needed

Add strategic operations or hub pages to human-readable and AI-readable discovery files.

Output: Discovery diff

Record release notes

Document affected area, version, rollback path, and validation evidence.

Output: Release note

Refresh and Pruning

Improve existing pages before adding unnecessary new pages.

3 steps

Refresh declining pages

Use GSC trends to identify pages losing impressions, CTR, or ranking coverage.

Output: Refresh brief

Consolidate duplicate intent

Merge or redirect overlapping topics when pages compete for the same search intent.

Output: Content merge note

Archive content evidence

Save query source, edits made, review notes, and post-update monitoring date.

Output: Content changelog

Blog publishing gate

Blog Draft SEO Review

The user writes or approves the blog article body; AI reviews, formats, validates, and publishes only after approval.

npm run seo:blog-review -- --file path/to/draft.md --keyword "primary keyword"npm run seo:blog-evidence-validate -- blog-review-result.jsonnpm run seo:blog-ready -- --file path/to/draft.md --keyword "primary keyword" --output blog-ready-result.json

Hard checks

Primary keyword appears within the first 100 words.
Primary keyword appears within the final 100 words.
Draft has at least 800 words.
Exactly one H1 appears on the page.
Heading levels do not skip from H1 directly to H3 or deeper.
H1 contains the primary keyword.
At least one H2 contains the primary keyword when it reads naturally.
Every uploaded image includes descriptive alt text.
Draft avoids personalized recommendations, best/optimal claims, guarantees, fake ratings, risk-free claims, and 100% accuracy claims.
Draft includes at least one internal link to the calculator or a relevant supporting guide.
Draft includes at least one official source link for tax, Medicare, ACA, Social Security, or government rule context.

Manual review

1,500+ words is preferred for blog articles when the topic supports it.
Keyword density target is reviewed as 2% to 4% without keyword stuffing.
H2 sections form the article outline; H3 and H4 support real subsections.
Normal body text is represented as paragraphs, not oversized heading text.
Strong emphasis is reserved for important terms or high-value phrases.
Additional tax, Medicare, ACA, IRS, and state-tax claims stay source-aligned and educational beyond the required official source link.

AI publication duties

Add metadata, canonical URL, Article JSON-LD, and Breadcrumb JSON-LD from real article data.
Add sitemap, RSS, llms.txt, and internal-link discovery paths when the article is approved.
Retain and validate the blog review JSON evidence before engineering publication.
Use the one-step readiness command for quick pre-publication checks when a retained JSON file is not needed yet.
Treat `manual-review-required` as a stop for editorial review; publish only after the final reviewer accepts the remaining manual signals.
Run blog review, YMYL language tests, production build, SEO smoke, and structured-data evidence before release.

Final release gate

Final publication review

Use this gate after the user finishes or approves the article body, before AI turns the draft into a published route.

npm run seo:blog-final-validate -- --path /blog/approved-slug --readiness blog-ready-result.json --smoke seo-smoke-result.json --structured-data structured-data-evidence-result.json --blog-discovery blog-discovery-evidence-result.json --output blog-final-publication-result.json

npm run seo:blog-publication-manifest -- --path /blog/approved-slug --readiness blog-ready-result.json --final blog-final-publication-result.json --smoke seo-smoke-result.json --structured-data structured-data-evidence-result.json --blog-discovery blog-discovery-evidence-result.json --output blog-publication-manifest.json

npm run seo:blog-publication-manifest-validate -- --manifest blog-publication-manifest.json

Required evidence

`blog-ready-result.json` with `ok: true` and a reviewed publication status.
`blog-review-result.json` retained when a separate reviewer handoff or release package is needed.
`blog-final-publication-result.json` retained after final package validation.
`blog-publication-manifest.json` retained as the evidence inventory for the article release package.
Manifest validation output confirms retained evidence file hashes still match.
Confirmed internal link target and at least one official source link in the article body.
Article metadata, canonical URL, Article JSON-LD, and Breadcrumb JSON-LD derived from the approved article data.
Post-deploy production evidence from SEO smoke, structured-data evidence, blog discovery evidence, sitemap, RSS, and llms.txt.

Stop conditions

The article body has not been written or approved by the user.
`publicationStatus` is `manual-review-required` and the remaining manual signals have not been accepted.
Any hard check fails for heading hierarchy, image alt text, YMYL language, internal links, or official source links.
The draft uses personalized tax advice, best/optimal claims, guarantees, fake ratings, risk-free claims, or 100% accuracy claims.
The article introduces tax, Medicare, ACA, Social Security, or state-tax claims that are not source-aligned.

Publish criteria

The user-approved body is the source of truth for the article text.
Hard checks pass, and any manual-review-required items are explicitly resolved before release.
The new URL is reachable from the blog hub and included in sitemap, RSS, and llms.txt when appropriate.
Production structured-data evidence includes the new blog page with Article and BreadcrumbList.
Release notes and progress records include rollback path, validation commands, deployment URL, and retained evidence artifact.

Operating Outputs

Keyword briefEditorial queueDraft pageInternal link checklistSEO checklistCompliance reviewSource noteSitemap diffDiscovery diffRelease noteRefresh briefContent merge noteContent changelog

Open guides Open site index

This Roth Conversion Calculator is for educational and illustrative purposes only. It does NOT constitute tax, financial, legal, or investment advice. The calculation results are based on the information you provide and the latest IRS tax rules, which are subject to change. We do not guarantee the accuracy of the results. Please consult a licensed Certified Public Accountant (CPA), financial advisor, or tax professional before making any financial decisions.