When building a new website, check the testing environment, URLs and page markup, search engine crawling settings, and plans for tracking after launch. If you are redesigning an existing site, also check that redirects work correctly and data collection can continue. The priority before launch is not simply to add a few keywords. Confirm that development settings are not blocking pages intended for public access, that URLs and markup match the plan, and that any issues found have been resolved. These are development checks, not guarantees of rankings.
Create a testing environment that is not publicly accessible
Give SEO staff access to the staging site during development so they can crawl pages and report issues, rather than waiting until all the page layouts are complete. If a live site already exists, you can copy its files and database to create a testing environment. Make sure the staging site uses the copies. If the live site uses a CDN, also verify compatibility on the staging site.
- Password-protect the staging site, adding an IP allowlist and noindex if needed to prevent unfinished content from being exposed publicly.
- Include SEO requirements in development tickets. Regularly discuss progress on fixes, verify the results, and update the records.
Define the URL structure first; map old URLs to new ones for a redesign
First, confirm whether the URL structure is constrained by the category hierarchy or platform, and whether changes require a developer’s help. If you are only changing domains, you do not necessarily need to change the URL structure as well. You only need to map individual old URLs to new ones when an existing site needs to be migrated. For example, Procrustes builds a separate website as part of its service, without requiring changes to the client’s existing official website.
Test redirects to confirm that they lead to the correct final destination, and check for problems such as redirect loops or destination pages that no longer work. If image locations change, also consider redirects for the old image URLs. Verify that tracking parameters used in ads, social media, or email are preserved as well.
Check page markup and whether the content management system supports ongoing maintenance
When crawling the staging site, check page titles, meta descriptions, H1 headings, URLs, and canonical tags. If there are multiple language versions, check hreflang as well. Titles and descriptions can be written individually, generated programmatically, or handled through a combination of both, depending on your needs. If many need to be written individually, first confirm whether the content management system (CMS) supports bulk uploads.
- Canonical tags should point to the intended preferred versions of pages. Incorrect settings can cause duplicate-content problems or affect crawl efficiency.
- Image alt text should describe the image so screen reader users can understand its content.
- Plan and validate structured data early. The markup needed varies by website and industry; the same set does not apply to every site.
Run an actual crawl before launch, rather than just reviewing a settings checklist
Create and test robots.txt. Confirm that crawl restrictions apply only to the intended locations, and check whether CSS or images have been blocked by mistake. You can use a crawler configured with Googlebot’s user agent to identify problems, but the simulation results do not guarantee that search engines will index the pages.
The redesign guide recommends checking the XML sitemap before launch and including only URLs that return a 200 status code and have self-referencing canonical tags. A 2018 content launch checklist also advises removing noindex directives left over from development on public pages you want search engines to index.
If you are migrating an existing site, also check the verification settings for analytics and search platforms. Make sure data collection can continue so you can assess performance after the switch.
SEO checks for a new website: perspectives from across the web
Should you check loading speed before launch?
Yes, especially for content pages you plan to promote publicly. A 2018 content launch checklist recommends using Google Lighthouse to establish a performance baseline, because slow-loading pages may cause visitors to leave before they see the content. Test results can help track improvements, but reaching a particular score does not guarantee rankings.
Should content pages link to other pages on the site?
You can add links from a piece of content to related pages on the same site. Screaming Frog noted in 2018 that external coverage usually links to the content itself, so internal links can help pass link equity. Links should still be planned around relevance, rather than added arbitrarily just to increase their number.
Should you also check navigation and access to contact information?
These are worth checking. A 2004 article offering website-building advice recommended providing a back-to-top link at the bottom of each page and a contact link in each page's header or footer. The former helps visitors return to the top, while the latter makes it easy for people to find a way to get in touch. This is user-experience advice, not a mandatory rule imposed by today's search platforms.
References
- The Complete Website Migration Checklist [SEO-Friendly]www.semrush.com · 2019-03-25T13:30:00Z — Source used in the article above.
- Interactive Content Launch Checklist – 12 Things to Do Before You Send It to the Clientwww.screamingfrog.co.uk · 2018-05-14T14:01:58+00:00 — Discusses: Should you check loading speed before launch?; Should content pages link to other pages on the site?
- Website Usability & Search Engine Optimizationwww.searchenginejournal.com · 2004-02-07T01:43:42+00:00 — Discusses: Should you also check navigation and access to contact information?
- Website Migration SEO Checklist (88 Steps + Free Template)backlinko.com · 2024-04-01T17:23:50-05:00 — Source used in the article above.
