An SEO roadmap for a new product: the first year by quarter

Write the strategy first. One page. It answers three questions.

• Which searches you want: the category and best-of lists, the alternatives and comparisons, the jobs the product does, the integrations, the brand.
• Which pages will answer them: one page per topic, not ten half pages.
• How the site will earn links and mentions: launches, listings, tools, data.

Write it once a year. Read it every month. Keep it short so you do read it.

Turn that into a plan. The plan adds dates and an order. It lists the pages to write this quarter, the pages to refresh, the technical debts to clear, and who does what.

Your roadmap is the plan drawn over quarters. The rest of this page is that roadmap. Copy it, then adjust the topics to your product.

Pick one KPI you will read weekly. Pick the metrics you read when that KPI moves. Keep the dashboard simple. Search Console can be the dashboard for most small sites. Looker Studio connects to Search Console and GA4 for free if you prefer a single view.

You will lay the foundations and publish your first ten pages. Ship a clean site that can be crawled, that loads fast, and that answers basic intent. Expect indexing to settle and early impressions to start. Clicks will be sparse at first. That is normal for a new product.

1. 1

   Set up the basics

   Verify Search Console. Submit your sitemap. Fix crawl blockers that should not be there. Make sure important pages are indexable and reachable in two clicks from the home page.

2. 2

   Fix Core Web Vitals to sensible targets

   Aim for 2.5 seconds for LCP, 0.1 for CLS, and 200 ms for INP. Cut large images, third party scripts, and render blocking code. Use PageSpeed Insights to find the worst offenders.

3. 3

   Choose the first ten topics

   Use your strategy. Pick one homepage, one /pricing, one /guides/getting-started, two feature pages, two job to be done pages, one integration page, one brand story or about, and one article that answers a clear non brand query.

4. 4

   Write one page per topic

   Write for the query. Include the exact question or task in the title and h1. Keep titles under about 60 characters. Add a meta description that reads like a result, 120 to 155 characters.

5. 5

   Structure for internal links

   Link from the home page and /pricing to the key features and jobs pages. Link the getting started guide to relevant features. Add breadcrumbs if the site has depth.

6. 6

   Add schema where it helps

   Mark the organisation on the home page, and the product or SoftwareApplication on product pages. Use FAQ schema on a genuine questions section if you have it.

What to expect in figures. Indexed pages count up as Google crawls. Impressions start on brand terms and on longer questions. Average position moves a lot week to week. Do not chase it. Your KPI could be non brand clicks per week, even if the first month is at zero. Write a goal for the end of the quarter, like two hundred clicks a week from non brand searches by March. Adjust the figure to your niche once you see real data.

• Week 1: Verify Search Console, connect GA4, submit the sitemap, and check indexation of the home page and /pricing.
• Week 2: Fix any noindex or robots.txt mistakes. Ship a clean robots.txt and an XML sitemap.
• Week 3: Write /guides/getting-started. Link it from the header or footer.
• Week 4: Write a jobs page, like "/use-cases/automated-reports". Link it from the home page.
• Week 5: Write a feature page, like "/features/scheduled-exports". Add internal links from related pages.
• Week 6: Write the integration page, like "/integrations/google-sheets". Link it from features.
• Week 7: Write a second jobs page. Add a short case example if you have one.
• Week 8: Write a second feature page.
• Week 9: Write the first article for a clear question, like "how to schedule csv exports". Keep it specific to your product’s space.
• Week 10: Tighten titles and meta descriptions using the title and meta length guides. Add alt text to images.
• Week 11: Fix Core Web Vitals issues still flagged. Compress images and lazy load where safe.
• Week 12: Review the KPI and metrics. Note what shipped. Write the one page monthly report and set next month’s focus.

A fixed page at the end of Q1 looks like this: a clear title that reads like the query, a first paragraph that answers it, simple headings, one focused call to action, and two or three internal links to deeper pages. Nothing thin or duplicated. No index bloat.

Now build families of pages and run launches. Families earn when each page holds its own answer or data. Launches earn links and mentions. Expect impressions to rise across a cluster when you cover a topic well. Clicks from non brand terms should begin to hold week on week if the pages match intent.

1. 1

   Expand each family

   If you shipped "/integrations/google-sheets" add pages for other real integrations you support. If you shipped one jobs page, add two more jobs that your customers ask for. Keep one page per topic.

2. 2

   Interlink the cluster

   Link laterally within a family. Add a short overview hub if it helps users, like "/use-cases/" or "/integrations/". Do not create empty hubs.

3. 3

   Answer adjacent questions

   Write three to five articles for clear questions your support inbox sees. Use the words your users type. Link each article to the relevant jobs or feature page.

4. 4

   Plan and run two launches

   Pick one major launch, like a product update with a public demo. Pick one directory or community listing relevant to your space. The aim is mentions, not just traffic spikes.

5. 5

   Collect proof on pages

   Add testimonials, short quotes, or a simple chart to "/pricing" and the jobs pages. It helps both conversion and citations when others link to you.

6. 6

   Optionally run PPC on high intent queries

   Use a small budget to test which queries convert. Use those terms in your page titles and copy once they prove out. Paid stops when the budget stops. Organic holds them once you rank.

What to expect in figures. Families tend to increase impressions together. You may see more queries per page in Search Console. Average position stabilises on some long tail terms. Your KPI should start to move. Keep weekly notes on which pages drive the change. Use the performance report to filter by page family and by query contains the integration or job name you target. Adjust Q3 plans based on what users actually click and sign up from.

Refresh early work and earn links with things worth citing. Expect steadier clicks if you prune and improve. One good link from a relevant site beats ten weak ones. This is the quarter to remove or merge redundant pages and to publish data or tools that others reference.

1. 1

   Run a light content audit

   List pages with impressions but poor clicks. Tighten titles and meta descriptions. Improve the first screen of content so the answer is clear without scrolling.

2. 2

   Refresh the top five pages

   Add missing steps, current screenshots, or a short video. Update dates if you republish. Keep the URL if the topic is the same.

3. 3

   Merge or delete thin pages

   If two pages answer the same query, pick the stronger one and 301 redirect the weaker to it. Avoid keyword cannibalisation.

4. 4

   Publish something citeable

   A small dataset from your product, a calculator, or a generator tied to your space. Host it under "/tools/" or "/data/" and explain the method.

5. 5

   Ask for links where relevant

   If a blog mentions you without a link, ask politely to add one. If a partner lists integrations, make sure your integration page is linked. Avoid buying links that pass ranking.

6. 6

   Tighten internal links

   Use the articles to point to the jobs and features that convert. Add a short related reading section at the end of each article.

What to expect in figures. Click through rate should improve on refreshed pages. The number of referring domains may tick up. Average position climbs on pages that now satisfy intent better. Your KPI should grow more from a smaller set of pages. Keep the monthly report to one page so you can see the trend and decide the next refresh list quickly.

Now publish alternatives and comparisons, and make your answers easy to cite in AI overviews. These pages convert. They also carry risk if you copy formats at scale without value. Expect higher intent clicks if you get this right. Handle them with care and with evidence.

1. 1

   Write alternatives pages

   A page like "/alternatives/tool-x" helps searchers who are open to change. Be fair. Compare on criteria users care about. Show where you fit and where you do not.

2. 2

   Write comparison pages

   A page like "/compare/you-vs-tool-y" meets very high intent. Structure it with a quick summary, a side by side table, and links to docs that prove claims.

3. 3

   Collect and cite sources

   Link to your docs and to public pages for rivals’ features or pricing if you mention them. Keep tone factual. Do not disparage.

4. 4

   Target People also ask and snippets

   Add short Q and A sections for common sub questions. Use the exact wording users type. Mark up with FAQ schema when the page genuinely answers discrete questions.

5. 5

   Prepare for AI overviews and answer engines

   Write clear, citeable paragraphs that state the answer first. Use descriptive headings. Add a concise summary box that an AI could quote. Consider a simple tool or data point that no one else has.

6. 6

   Keep scope sane

   Publish a handful of solid comparisons, not dozens of thin ones. Each page must hold an answer or data of its own that a reader would want.

What to expect in figures. Queries with brand and rival names can bring qualified clicks. Monitor signups from these pages closely. If they convert, link to them from the home page footer and relevant feature pages. If they do not, refine the copy to match how users decide. Watch for mentions and AI citations as a side effect of clearer answers.

Pick one KPI and stick to it for a quarter. For a new product, a good KPI is clicks from non brand searches per week, or signups from search per week. Read it every week. When it moves, ask which pages and which queries drove it. That is where you double down.

• KPIs: clicks from search, signups from search, revenue from search.
• Diagnostics: impressions, average position, indexed pages, Core Web Vitals, referring domains.

Use Search Console’s performance report to filter by page and by query. Save simple filters, like queries contains "google sheets". Add a Looker Studio view if you want a single page with GA4 signups next to clicks. Keep it light so you actually look at it weekly.

Your monthly report fits on one page. It holds what changed in the KPIs and why, what was shipped, what the next month does, and the figures as a small table. Send it to yourself. If you have a team, read it together for fifteen minutes and agree the next steps on the call itself.

DIY SEO is realistic for a founder with free tools and one hour a week. You can set up Search Console, review the results page, and ship pages. What you cannot do is write forty good pages a month or earn links without a product worth linking. Be honest about that trade off.

• A consultant sells judgement: an audit, a strategy, or a review of work.
• An agency sells execution across writing, design, and links.
• An in house hire sells continuity and context.
• A report sells the judgement once.

Pricing varies by country, by scope, and by the seller. Agencies often bill retainers. Freelancers bill hourly, daily, or per project. Tools bill monthly. Any number claimed as the average is somebody’s marketing. Size your budget by the work, and by the value of a search click to your business.

If you want a one off report, Porteur is one option. It is bought once, and you pick the version with or without product analytics. Or hire a consultant for a day to write your strategy and first quarter plan. Do what gets you shipping pages fastest with the quality you need.

Google does not penalise AI assisted writing as such. It acts on pages made at scale without value of their own. If you use AI to draft, add your own data, examples, and screenshots. Publish fewer, better pages. Do not chase quantity for its own sake.

• Do not produce many near duplicate pages that only swap a word or a city name.
• Do not host third party content just to exploit your domain’s strength.
• Do not buy expired domains to carry unrelated content.

A safe pattern is a page family where each page holds data or an answer of its own that a reader would want. For example, five integration pages with real setup steps and limits, not just a template that repeats itself with a logo swap. That earns over time and stays within policy as of 2026.