Gale Atlas

Weekly growth routine

Turn Search Console screenshots into useful page updates.

Gale Atlas should grow from search data, not guesswork. This weekly workflow turns your screenshots into a short, ranked task list for titles, FAQs, internal links, indexing fixes, and long-tail guides.

Search Console screenshots

Last 28 days performance overview, queries, pages, and indexing summary.

Current priority pages

Pages with impressions, positions 8-30, low CTR, or indexing warnings.

Recent site changes

New guides, tools, internal links, source checks, and AdSense review notes.

Screenshot handoff protocol

A small weekly packet is enough to make good decisions.

The goal is not to inspect every dashboard screen. A consistent packet lets Gale Atlas improve titles, links, FAQs, and new long-tail pages from real search behavior while staying calm during AdSense review.

View 6-screenshot packet

Packet label

Send the message as "Gale Atlas weekly SEO check" so the screenshot set is easy to find later.

Date window

Use Last 28 days unless we are checking a launch week or a specific deployment.

First pass

I will separate CTR fixes, rank-push pages, indexing problems, and new long-tail gaps.

Task limit

The weekly output should stay at 5-10 tasks so the site improves without random churn.

After deploy

Run production smoke, then wait for Search Console to refresh before judging the impact.

SEMrush keyword packet

Use SEMrush to choose pages before we write them.

Search Console tells us what Google already sees on Gale Atlas. SEMrush helps decide which Windrose and second-game pages are worth creating before the site has enough impressions. Send the US database first, then Global if available.

Candidate worksheet

Keyword

The exact query text, not a grouped topic label.

Volume

US volume first, then Global if available. Low volume is still useful when intent is sharp.

KD%

Keyword difficulty helps separate quick long-tail wins from authority battles.

Intent

Prefer informational, commercial-support, troubleshooting, and comparison intent over thin news intent.

Trend

Watch launch spikes, fading hype, and steady evergreen support searches.

SERP URLs

Top results reveal whether the query is already solved or still has weak forum/thin-page coverage.

How I will score SEMrush data

Volume 20-500, KD low or medium

Create or upgrade a focused long-tail guide if the query has a clear player problem.

Top 10 results are forums, Steam threads, Reddit, or thin posts

Prioritize a practical guide with a clear answer, FAQ, internal links, and source labels.

Query contains server, save, crash, settings, co-op, or requirements

Treat it as a high-fit Gale Atlas page candidate before broad news or wiki-style terms.

High volume, high KD, generic wiki or release-date term

Do not chase first. Use it only as hub support or a future cluster anchor.

Several non-Windrose terms cluster around the same new game

Move the evidence into the second-game candidate worksheet before opening a new hub.

Prioritization rules

Pick tasks by signal strength.

CTR fix

High impressions, low CTR

Rewrite title, meta description, first answer, and FAQ wording.

Rank push

Average position 8-30

Add a sharper answer block, related tool link, and 2-3 internal links.

Index fix

Submitted but not indexed

Check thin content, canonical signals, sitemap presence, and duplicate wording.

New long-tail

Repeated query with no exact page

Create one narrow troubleshooting or setup guide for that query.

Expansion signal

Windrose query volume stays weak

Compare the next game candidates before opening a second hub.

Search signal decision matrix

Turn each Search Console pattern into the first sane action.

This matrix keeps weekly SEO work focused. The first move should be small, measurable, and tied to the signal in your screenshot before Gale Atlas adds more pages.

Signal

Impressions up, CTR below 1%

First action

Rewrite the title and first answer before creating a new page.

Done check

Next week should show a better CTR for the same query group.

Signal

Average position 8-15

First action

Add a direct FAQ answer, one related tool entry, and links from the hub or topic page.

Done check

Next week should show more clicks or movement toward page-one visibility.

Signal

Average position 16-30

First action

Expand the guide with missing steps, screenshots or labeled media, and 2-3 internal links.

Done check

The page should gain broader query coverage before expecting a CTR jump.

Signal

Submitted URL not indexed

First action

Check sitemap presence, canonical URL, thin sections, duplicate wording, and crawlable internal links.

Done check

Index status should change before requesting more aggressive content expansion.

Signal

Repeated query has no matching page

First action

Create one narrow long-tail guide only when the query is specific and reusable.

Done check

The new page should enter the sitemap, search index, RSS context, and internal-link map.

Signal

Several queries point to another game

First action

Move the idea into the expansion research board instead of mixing games inside Windrose pages.

Done check

Second-game work should pass demand, competition, long-tail depth, and tool-fit gates.

Weekly output

What I should produce after your screenshots.

5-10 page-level tasks ranked by traffic upside.

Exact title or FAQ changes for pages with weak CTR.

Internal-link additions from hub, topic, tool, or related guide pages.

New long-tail page ideas only when Search Console shows a real gap.

Indexing fixes before requesting more Google recrawls.

Task template

Every weekly task should be specific.

Page

The exact URL to change, or NEW if the query needs a new guide.

Signal

Screenshot evidence: query, impressions, CTR, average position, or index issue.

Action

Title rewrite, FAQ add, intro answer, internal link, tool entry, or new page.

Why now

The reason this task has better upside than writing random new content.

Done check

What should be verified after deployment and in next week Search Console data.

Four-week cadence

Keep the site calm while AdSense reviews it.

Advertising policy

1

Week 1: confirm indexing and protect AdSense review stability.

2

Week 2: improve titles and first answers on pages with impressions.

3

Week 3: add FAQs and internal links to pages ranking 8-30.

4

Week 4: create only the missing long-tail pages proven by query data.

During AdSense review, do not chase every idea. Fix crawlability, strengthen pages already getting impressions, and keep affiliate or aggressive ad experiments out of the early growth loop.