Search Console launch chart

Keep Gale Atlas crawlable, useful, and review-ready.

Use this checklist after each Windrose deployment: submit the right URLs, watch the right signals, and keep patch-sensitive claims labeled until they are verified.

103

published guide pages

159

searchable entries

free planning tools

Pre-submit checklist

1. Confirm https://www.galeatlas.com is the preferred live URL and the apex redirects cleanly.
2. Open /robots.txt and verify it points to https://www.galeatlas.com/sitemap.xml.
3. Open /sitemap.xml and confirm the Windrose hub, search page, tools, topic pages, and fresh guides are listed.
4. Run the production smoke check after every deployment before requesting new indexing.
5. Keep privacy, terms, contact, about, disclaimer, editorial policy, media sources, and advertising policy reachable from the footer.
6. Submit the domain property and sitemap in Google Search Console.
7. Request indexing only for the highest-value URLs first instead of every page at once.
8. Check indexing status weekly and fix crawl, duplicate, soft-404, or blocked-resource issues before writing more pages.

Weekly signals

Indexing

Submitted vs indexed pages, excluded reasons, sitemap discovery, and canonical selection.

Queries

Look for server not showing, direct join, save missing, can I run it, FPS, and co-op terms.

Pages

Find URLs getting impressions but low clicks, then improve titles, intros, and internal links.

Freshness

Update Early Access pages when official data, patches, or guide verification changes.

Weekly screenshot packet

Send these 6 screenshots in this order.

Name the message "Gale Atlas weekly SEO check" and attach the screenshots in order. I can then turn the packet into title rewrites, FAQ additions, internal-link tasks, indexing fixes, or new long-tail guide ideas without needing dashboard access.

See task workflow

Performance overview

Last 28 days with clicks, impressions, CTR, and average position visible.

Queries by impressions

Top queries sorted by impressions, including low-click terms and average position.

Pages by impressions

Top URLs sorted by impressions so pages with weak CTR or positions 8-30 are visible.

One priority page drilldown

Open one important URL, then screenshot its query table for exact title and FAQ work.

Indexing status

Pages indexed, not indexed, duplicate, crawled but not indexed, and canonical warnings.

Sitemap status

Submitted sitemap row, discovered URLs, last read date, and any sitemap processing warnings.

First-stage review packet

What to send on June 10, 2026.

When the first review reminder fires, send this compact packet instead of trying to analyze the dashboards yourself. I will use it to choose the next optimization tasks and decide whether we keep tightening Windrose or start evidence-based second-game research.

Review status Ad policy

AdSense status

Send the site detail screen for galeatlas.com showing approved, in review, rejected, or needs fix. Revenue screens are optional.

Search Console performance

Last 28 days performance overview plus queries, pages, CTR, and average position. Sort queries and pages by impressions.

Indexing and sitemap

Send Pages indexing, Sitemaps, discovered URLs, last read date, and any duplicate, crawled but not indexed, or canonical warnings.

Manual actions and security

If visible, send the Manual actions and Security issues screens so policy or trust problems are caught before more publishing.

URL inspection sample

Inspect the homepage, Windrose hub, one guide, and one tool. Send screenshots only if Google says a URL is not indexed.

What I will return

A ranked list of 5-10 fixes: titles, meta descriptions, opening answers, FAQ blocks, internal links, or tool links.

A crawl and indexing fix list if Search Console shows duplicate, canonical, soft-404, blocked, or not-indexed issues.

A content decision: keep optimizing Windrose first, or start the second-game scoring table with evidence.

An ad decision: stay conservative, adjust placements after approval, or fix policy issues before adding anything new.

Do not send secrets

Do not send passwords, API keys, Vercel tokens, DNS login details, payment details, or private account recovery screens.

The public AdSense publisher ID already in ads.txt is fine; private revenue, bank, tax, and identity screens are not needed.

Screenshots are enough. I only need status, queries, pages, indexing reasons, sitemap state, and visible policy messages.

Weekly SEO workflow Public update log

Weekly screenshot guide

Send these Search Console screenshots once a week.

Use Google Search Console performance data instead of guessing. The screenshots should show the last 28 days so we can pick 5-10 page updates with the best chance of raising search traffic.

View expansion research Weekly SEO workflow

Performance overview

Set date range to Last 28 days. Screenshot total clicks, impressions, average CTR, and average position.

Queries table

Sort by impressions. Screenshot the top queries, especially terms with impressions but weak clicks.

Pages table

Screenshot pages with impressions. Mark pages ranking around positions 8-30 for title, FAQ, and internal-link work.

Indexing summary

Screenshot indexed, not indexed, sitemap discovery, duplicate, soft-404, blocked, or canonical warnings.

How I will use your screenshots

If a page has impressions and low CTR, improve the title, opening answer, and search-intent wording first.

If a query ranks position 8-30, add a tighter section, FAQ, tool link, or related guide path before writing unrelated pages.

If pages are not indexed, fix sitemap, canonical, duplicate, thin-content, or crawl issues before requesting more indexing.

If Windrose demand looks thin after several weeks, keep it as the first asset and compare the next game on the expansion research board.

Owner dashboard map

Know which dashboard answers which launch question.

View public update log

Vercel project

Check production deployments, domain status, Vercel Analytics, and Speed Insights after each release.

Open Vercel

Search Console

Watch indexing, clicks, impressions, CTR, average position, page queries, and sitemap discovery.

Open Search Console

Google AdSense

Check site review status, policy messages, ad readiness, payment setup, and future revenue reports.

Open AdSense

Keep passwords, API keys, Vercel tokens, Search Console ownership files, and AdSense account details out of public pages and chat. This map stores only safe dashboard destinations.

Priority URL queue

Request these first when crawl budget is limited.

Open sitemap

1Homepage/2Windrose hub/games/windrose 3Search Windrose guides/search 4Start Here roadmap/start-here 5Tools hub/tools 6Server browser and direct join/guides/windrose-server-browser-direct-join-guide 7Server not showing up/guides/windrose-server-not-showing-up-guide 8Save missing recovery/guides/windrose-save-missing-recovery-guide 9Can I Run Windrose?/guides/windrose-can-i-run-it-guide 10PC readiness checker/tools/windrose-pc-readiness-checker 11Multiplayer issue router/tools/windrose-multiplayer-issue-router 12Advertising policy/advertising-policy

Claim guardrails

Do not publish exact ports, commands, provider buttons, config paths, save paths, or file steps without current-build verification.

Keep exact map markers, material costs, recipe values, boss drops, and route names marked as pending until checked.

Avoid aggressive ad placement while AdSense review is pending; useful navigation and readable content come first.