You've worked through the earlier chapters and you're holding a list of improvements long enough to paralyse you. The first month isn't about ranking anything. It makes sure the site can rank at all and puts today's numbers on paper before you change them. It also settles the searches that the next sixty days get built around. Do those in order and every page you publish later lands on a site Google reads fully, with a baseline to measure it against.
Why the first month is for fixing
Every page goes through the same pipeline. Google finds it, stores it, then ranks it, as How Google ranks a page explains. A new page on a site with a stray noindex, a broken sitemap or a slow template inherits every one of those faults. Fix them once before the content work starts, and you avoid fixing them under twenty new pages.
The baseline matters for a duller reason. In three months you'll want to know whether the work made a difference, and you can only answer if you wrote down where things stood first. Reading rank movements honestly needs a day-one snapshot to compare against.
Keywords come before writing because writing first is how a site ends up with four pages chasing the same search. Thirty days gives you four working weeks and a couple of spare days for whatever slips.
Week 1: audit and take the baseline
Three jobs, in this order.
- Get measurement in place. Verify the site in Google Search Console and make sure GA4 is collecting. Google Search Console essentials and GA4 for SEO walk through both. If either already exists, check that it covers the whole site, www and non-www.
- Write the baseline on one sheet. Record the pages Search Console reports as indexed and your clicks and impressions for the last few months. Add your top twenty queries and pages, plus your position for the searches you care about most. Then add an AI row. Ask ChatGPT and Gemini what a customer would ask, note whether either names you, and follow Measuring your AI visibility for the method.
- Find the blockers. Run The 30-minute quick-wins audit, then check the plumbing in Sitemaps, robots.txt and indexing. You're looking for robots rules and
noindextags first. After those come the sitemap, redirect chains and canonicals, and finally broken pages and slow templates.
By day 7 you should have Search Console and GA4 collecting data. You should also hold a baseline sheet and a blocker list.
Week 2: fix the blockers in order
Work through the list by what stops Google seeing a page. Ease of the fix comes second.
- Crawling and indexing first: robots rules,
noindextags and sitemap errors. Redirect chains or loops on money pages belong here too. - Duplicates next. Parameter URLs and trailing-slash variants each need one canonical, and so do near-identical pages.
- Titles and meta descriptions on your most important pages, following URLs, titles and meta descriptions. Missing and duplicated ones go first.
- Speed on your key templates. Core Web Vitals explained covers the fixes. By web.dev's Core Web Vitals thresholds, a page is good when its Largest Contentful Paint is 2.5 seconds or under. The Interaction to Next Paint limit is 200 milliseconds, and Cumulative Layout Shift must be 0.1 or under. All of it is measured from real visitors.
Most of these are small developer tasks and none needs a redesign. Write each one up with the URL, the problem and the fix, hand it over with a date, and keep cosmetic requests off the list.
By day 14, every page you care about should be crawlable and indexable with one canonical URL. Anything still with the developer should sit on a dated list.
Week 3: choose the keywords you'll build around
Start with Keyword research from scratch, which takes you from your services to a long list of candidate searches. Then cut it. Search intent tells you which searches your kind of page can satisfy. The buying-intent ladder sorts them by how close the searcher is to paying, and the free Keyword intent checker runs that sort on a pasted list.
Finding competitor keyword gaps then shows the searches your rivals rank for and you don't. Early wins usually sit there.
Keep the shortlist to what you can serve in sixty days. A hundred keywords you never write for is a spreadsheet and nothing more.
By day 21 you want a shortlist grouped by subject. Each entry carries an intent and a rough sense of how hard it is to win.
Week 4: map keywords to pages and start the clock
Mapping keywords to pages gives every page one primary keyword and splits the shortlist into pages that exist and pages you need to create. Site architecture and internal links decides where the new ones sit and which hub links to them.
Then start the routines that run for the rest of the plan.
- Add the shortlist to rank tracking now. History starts the day you add a keyword, and a trend needs a starting point.
- Put a weekly review in the diary and use A weekly SEO review with Claude as the format.
- Draft the calendar for days 31 to 60. Order it by the buying-intent ladder and group it into the subjects Topic clusters will turn into clusters.
By day 30 you hold a keyword map and a running rank tracker. You also have a dated calendar for the next eight weeks and a weekly review slot.
Frequently asked questions
What is a SEO technique?
A technique is one specific action that helps a page get found or ranked. Fixing a noindex tag, giving a duplicate page a canonical and rewriting a title are all examples. A plan puts those actions in an order that makes sense, so the early ones don't get undone by later problems.
How to write an SEO strategy?
Begin with the site's health, then record a baseline, then choose keywords by intent. Map each keyword to a single page and schedule the pages you still need to create. Add a weekly review so you can see what the work is doing.
How can I research keywords for SEO?
List the services you sell and the questions customers ask about them, then expand each into candidate searches with Keyword research from scratch. Cut the list by search intent and by how close each searcher is to buying. Check what your competitors rank for that you don't, and keep only what you can write for in the next sixty days.
What to take away
- The first month fixes the pipeline and records the baseline, because every later result depends on both.
- Fix blockers by what stops Google seeing a page: crawling and indexing first, then duplicates, then titles and speed.
- Keep the keyword shortlist small enough to serve in sixty days and sort it by intent rather than volume.
- By day 30 you hold a keyword map, a tracker with a starting point and a calendar for the content engine.
Next
Days 31 to 60: the content engine turns the keyword map into published pages, one cluster at a time.