SEO checks to make before launching a website
By Pixit
A launch deserves more than one final look at the homepage. Search readiness also depends on less visible details: accessible pages, useful old links and complete language versions. This is the order we use to think through checks before a polished launch hides a closed door.
1. Check access to useful pages
Open each important page while signed out. Check its HTTP status and content. An empty page returning 200 is not ready to publish.
Make sure staging settings, including noindex, no longer block public pages at launch. Private areas must retain their protections: SEO is never a reason to expose them.
Choose a representative sample: homepage, service, article, form and each language version. Open them without an administration session. A page appearing correctly in your working account does not prove that an ordinary visitor can reach the same content.
2. Review titles and links
Each page needs a recognisable subject, its own title and an accurate description. Visitors should be able to reach useful content through links from the homepage or a section.
Click calls to action, language links and article links. Test an unknown URL too: it should return a real 404, not a disguised homepage.
Compare each title with the visible page. An appealing headline promising an absent answer mostly creates disappointment. Follow the links to neighbouring pages as well. A reader should be able to continue a subject without relying entirely on the main menu.
3. Plan URL changes
For a redesign, build a table with old URLs, destinations and reasons. Use permanent redirects when content has a genuine successor. Test the final destination and avoid redirect chains.
Include only selected canonical URLs in the sitemap. A retired page without an equivalent should not lead to an unrelated service merely to eliminate an error.
Keep the URL mapping beside the test list. Every important old address needs an explicit decision. The person deploying the site should not have to guess whether a discontinued service belongs on a page describing an entirely different offer.
4. Check languages and mobile use
Each language version should remain accessible at its own URL. Hreflang links connect equivalent versions; a French article should not identify the Hebrew homepage as its translation.
On a phone with a limited connection, try reading the page and submitting the form. Check oversized images, elements that move during loading and slow responses to interaction.
On a phone, start from a deeper page instead of the homepage. Read its heading, open the menu and follow an action. Repeat in another language. This checks whether someone arriving from search can understand the site without first seeing its introduction.
5. Verify after launch
Submit the sitemap in Search Console and inspect representative pages. A sitemap helps discovery but does not guarantee indexing. Monitor errors and changes after migration.
Keep the initial record of clicks, impressions and known pages. Compare the same languages over comparable periods. Successful technical checks are a starting point; results must then be measured on the live website.
Assign the follow-up and record the launch date. Otherwise a later change can be blamed on whichever paragraph was edited most recently. We want to answer two questions after release: what changed, and what was actually checked?
