Knowledge / Website SEO · 10 November 2026
Website SEO launch checklist: 12 checks before you call a site finished
A beautiful business website is not necessarily discoverable. Before launch, check that search engines can reach its useful pages, visitors can navigate them on a phone, and you can measure what happens after publication. This guide separates checks you can perform yourself from issues requiring a developer.
First, decide which pages deserve search visibility
For a small service business, a useful starter set might be Home, Services, About, Contact and a few genuinely helpful guides. Each page should have a distinct purpose. A location-specific page should describe a real service area and offer meaningful local information, not repeat the same paragraph with a different city name.
Make a simple spreadsheet with columns for page URL, purpose, target audience, primary question, title, canonical, internal links, indexability, test result and owner. That spreadsheet becomes your launch checklist and later change log.
The 12-point launch checklist
- Use the final HTTPS address. Choose one preferred hostname (for example, with or without
www). Test that other variants redirect to it and that links do not send visitors back to HTTP. Do not assume a browser padlock means every page or asset is configured correctly. - Check crawl access. Inspect
robots.txtand anynoindexdirectives. A staging site's noindex setting must not accidentally remain on public pages. Conversely, private account areas should not be exposed merely to improve SEO. Robots blocking and noindex are different controls. - Write a specific page title. A title should identify the page's real subject and brand without keyword repetition. Example: “Residential Solar Planning Services | Example Company” is clearer than “Best Solar Solar Solar Pakistan”. Search engines may display a different title.
- Add a useful meta description. Describe the page's benefit in natural language. A meta description is not a guaranteed ranking factor or a guaranteed search snippet, but it helps communicate intent when displayed.
- Use one clear main heading. Give each page an H1 that matches what the visitor expects. Use H2 and H3 headings for readable sections. Do not force every keyword into headings.
- Review canonical URLs. A canonical is a hint about the preferred version of duplicate or similar content. Make sure it points to the correct public URL rather than a staging address, unrelated page or accidental homepage. Canonical tags do not replace proper redirects.
- Make navigation and internal links useful. Link from relevant service pages to relevant guides and vice versa. Use descriptive anchor text such as “solar load planning guide”, not dozens of repeated exact-match phrases. Every important page should be reachable through normal navigation or contextual links.
- Test on an actual phone. Check menu access, tap target spacing, forms, input labels, text zoom, scrolling, image sizing and visible contact actions. An attractive desktop screenshot does not establish mobile usability. For a more detailed companion checklist, see the mobile-first website design guide.
- Review loading performance. Run PageSpeed Insights on representative pages. Look at real-user Core Web Vitals when available, not only one lab score. Optimize oversized images, render-blocking resources and unnecessary JavaScript only after identifying actual bottlenecks.
- Check accessible content. Use meaningful image alt text, associated form labels, visible focus states and sufficient contrast. Ensure the primary service explanation exists as readable text rather than only inside a graphic or animation.
- Submit a truthful XML sitemap. Include preferred, indexable URLs and accurate modification dates. A sitemap helps discovery but does not force indexing. Avoid including redirects, deleted URLs, login-only pages or duplicate URL variants by accident.
- Measure and verify after launch. Set up the site in Google Search Console, inspect priority URLs, review indexing reasons and monitor clicks, impressions and queries over time. If analytics is installed, test consent requirements and confirm events actually record without duplicating pageviews.
A worked example: a service page that is difficult to find
Suppose a construction consultancy has a page at /services/estimate/. The title is “Services”, the H1 is “Welcome”, the page has only a large hero image, and the homepage does not link to it. A search engine and a customer both have little context.
A better page explains the service in visible text: who needs a BOQ, what information the client must provide, what the deliverable includes, what is excluded and how to request a quotation. Its title might be “Construction BOQ & Cost Estimate Services | Example Company”. The H1 can be “Construction BOQ and cost estimate services”. Link to it from Services and to a useful BOQ omissions checklist. Keep the page accurate; do not invent prices, credentials, reviews or case studies.
Quick QA table to reuse
| Check | How to verify | Evidence to save |
|---|---|---|
| Canonical & redirects | Open HTTP, HTTPS and alternate hostname; inspect canonical in HTML | Final URL and response status |
| Indexability | Review robots and page directives; inspect URL in Search Console | Directive, inspection date and outcome |
| Mobile experience | Use a real phone for menu, form and readability tests | Device, issue and screenshot where appropriate |
| Performance | Test representative pages in PageSpeed Insights | URL, date, lab score and available field metrics |
| Internal links | Follow navigation and related-article links | Broken URLs and corrected destination |
| Measurement | Verify property ownership and test analytics events | Property, date and observed data |
What to do during the first month
First 48 hours: Verify priority URLs, redirects, forms and navigation. Record whether the sitemap is accessible and Search Console is configured. Do not interpret an initial absence of impressions as proof of a technical failure.
Week one: Review indexing reports and correct genuine errors, such as incorrect canonical targets, missing pages or accidental noindex tags. Recheck mobile navigation and real customer journeys.
Weeks two to four: Compare queries and landing pages in Search Console. Improve pages where search intent and actual content do not match. Publish useful new explanations only where there is a real information gap; do not create dozens of near-duplicate pages to chase keyword volume.
Common mistakes to avoid
“Sitemap submitted” is not “indexed”. The sitemap confirms a discovery hint, not Google's indexing decision. “CI passed” is not “live page checked”. A repository build may succeed while hosting is delayed or configured differently. Check the public URL and visible content separately. “SEO score 100” is not “rank #1”. Automated audits catch certain implementation issues; they cannot guarantee usefulness, trust or organic demand.
Frequently asked questions
Should I create a separate page for every keyword?
No. Group closely related queries by the visitor's underlying intent. A well-structured useful page can answer several related questions; separate pages make sense when the services or information needs are genuinely distinct.
Will a new site appear on Google immediately?
Not necessarily. Discovery, crawling and indexing timing vary. Submit accurate URLs, maintain internal links and monitor Search Console instead of assuming a fixed deadline.
Can I use AI to write my website?
AI can help draft and structure content, but someone familiar with the service must verify factual claims, local details, examples and whether the text genuinely helps customers. For design assets, read AI prompts vs editable design templates.
What should I improve first if I have limited time?
Fix pages that customers need but cannot access, then incorrect indexability or redirects, then confusing service explanations and broken conversion flows. Prioritize evidence from real users and Search Console over cosmetic score chasing.
Useful official references
Read Google's SEO Starter Guide, sitemap guidance, and Core Web Vitals overview for details. These resources explain general practices; they are not evidence that a particular site has passed an audit.
Explore the Pulse Hatch AI Website Studio for design workflows or browse the Knowledge Hub for more practical guides. Check any generated output carefully before publishing.