Make a New Product's Pages Easy for Search to Read

Search can bring someone to a page long after a launch post has gone quiet. It can also bring no one. Nothing here promises that a page will be indexed or that it will rank. The work is smaller: make a few useful URLs understandable to a person and to a crawler, then record what the tools actually report.

Google's SEO Starter Guide is the public reference to follow when a tutorial disagrees with it. The checks below are the small set that matters on a new product site.

One URL you would be glad to find

Choose a page that answers a job a stranger already has. A thin page created only to "hold a keyword" is a weak candidate. So is a second homepage with the words moved around.

On that URL:

• The title element says what the page is, in language close to the job. Do not reuse one title across the site.
• The visible heading agrees with the title. Someone who opens the page should meet the topic they were promised.
• The first screen says who it helps and what they can do next.
• The address stays stable. If the same content also lives somewhere else, choose one canonical URL and point the duplicate at it. A campaign parameter is a tracking detail, not a second official address.
• Links to your other pages use anchors that name the destination, and those destinations exist. A few relevant links are enough. A block of unrelated links does not create authority by volume.
• The page returns a normal success response, is linked from a page a crawler can already reach, and is not marked noindex unless you mean to hide it.

Write for the person with the problem. Use the words they use when those words are accurate. This guide does not assign keyword scores, search volumes, or difficulty numbers. Suggestions in a search box, and the queries you later see in Google Search Console, are enough to revise a title. Ignore any tool that offers a fake easy score for a phrase.

Check what the public page exposes

1. Publish an XML sitemap that lists only URLs you want found, including the page you just fixed. Open the file in a browser and confirm the addresses respond.
2. In Google Search Console, submit that sitemap and run URL inspection on the page. Write down the status it shows. "Unknown" or an exclusion is a finding. Inspection is not a forecast that you will rank.
3. Look for accidental copies: http and https, a trailing-slash twin, and a staging host that is still public. The canonical should name the one URL you mean.
4. Follow every internal link on the page. Fix the ones that 404. Landing page best practices is a solid explanation of how a launch page is put together. Link to it, or to your own equivalent, only when the reader needs that next step.
5. Later, read Search Console for queries that already show this URL. Improve a page that is close to useful. Do not order a stack of near-duplicate articles to chase a number you do not have.

If you use a hosted content service, confirm who maintains the article URLs, internal links, and sitemap. Check that useful pages are discoverable, and inspect Search Console for any property you control. Publication and search visibility are separate steps. The landing page analyzer explains the seven things a static scan looks at, and what that read cannot see. It is not a ranking report.

A launch post and a directory are different channels with a faster clock. The website launch checklist is the ship list. Treat search as the slow channel next to that list, not as the thing that has to spike on launch day.

Hypothetical example

**Hypothetical.** You have a homepage and one guide, "Export a CSV when the bank feed breaks," because three early users asked how. The guide's title matches its heading. The guide links to signup, and the homepage links back to the guide. You remove a second copy on a public draft subdomain. Search Console inspection says the guide is known, or it tells you the reason it is excluded, and you save that note. You do not write four more guides until someone outside your friends asks for the next job.

Copyable agent prompt

Audit one URL I paste for basic search readiness. Do not estimate traffic, keyword difficulty, or rankings. Do not claim any search engine will index or rank the page.

Check and report:
- Title and visible heading: do they describe the same specific topic?
- Canonical: is there one preferred URL? List duplicates you can see.
- Internal links: list broken links and vague anchors on this page.
- Indexing blockers visible in the HTML, including noindex or a canonical aimed at a different URL.
- Whether this URL appears in the sitemap I paste or link.

Give me a fix list I can apply by hand, in priority order, and the Search Console URL Inspection steps I should run myself. Do not change DNS, robots, or the sitemap unless I approve that file.

Finish rule

You are done with the basics when the preferred URL loads, its title and heading match the page, duplicates point at it, the sitemap lists it, internal links from it work, and you have saved the Search Console inspection result. You are not done "with SEO." You have made one page possible to understand. Whether it is indexed or ranked sits outside this checklist.

When the page is public, a free scan still helps with the visitor's view: whether the next action is clear, and which single gap a static review can name. The scan does not submit a sitemap, and it does not tell you how search will treat the URL.