# A technical SEO checklist for a new business site Begin with accessible pages, meaningful titles, correct status codes and a coherent link structure. Technical SEO helps search systems understand content but does not ensure rankings. A deleted service should not return the homepage with a success status; provide an appropriate replacement or a genuine missing-page response. Do not confuse successful deployment with confirmed search indexing. ## Start with the pages a visitor should actually find Create an inventory of the pages intended for public search: the homepage, genuine service details, useful articles and relevant supporting information. Give each a clear purpose. A page that exists only because a keyword was available is not automatically a useful addition. The inventory becomes the shared reference for navigation, the sitemap and launch checks. Open important pages directly, not only by clicking through from the homepage. Confirm that each intended address shows its own content and that a made-up address returns a real not-found response. If every unknown address returns the homepage with a successful status, the site is concealing errors rather than offering a coherent structure. Record redirects for any old pages that are being replaced. Then check that the main explanation is present in the delivered page, even before optional interactive features run. A service page whose entire content waits for a fragile browser request creates unnecessary uncertainty. A public page should also not demand an application-security challenge merely to read the service. The enquiry endpoint and public reading experience have different jobs. ## Make the visible story and the technical labels agree For each page, compare the browser title, main heading, description and actual text. They need not be identical, but they should describe the same subject. A title promising a price list should lead to accessible prices or a clear explanation of how pricing works. A generic title repeated on every service page misses the chance to explain the distinction between those services. Check the preferred address declared by the page and ensure internal links use it consistently. For multilingual pages, keep the current language as the canonical version and connect its genuine equivalents. A translated page should not silently nominate the English page as the preferred copy simply because English was developed first. Structured data should repeat facts the visitor can verify, not create a second, more impressive version of the business. If no reviews or legal company details are confirmed, do not manufacture them for search markup. The same rule applies to prices: a schema field and a visible package card should come from the same approved catalogue. These checks are easier when content and metadata share one model. ## Finish with a small evidence-based launch record Ask for a concise report covering public addresses, redirects, sitemap inclusion, robots behaviour, titles, canonical references and broken internal links. The report should distinguish “implemented” from “checked on the live domain.” A local build can prove many structural properties while leaving domain rules or search-console ownership unverified. Inspect a few representative pages manually after the automated checks. A technically valid link might still have an unhelpful label. An image might load correctly but obscure essential text. A page may be crawlable while containing almost no useful explanation. Technical SEO supports meaningful content; it does not compensate for the absence of it. After publication, observe discovery and indexing rather than promising a date or a position. Keep a record of meaningful changes so later search reports have context. A sound initial checklist gives the business a readable, maintainable foundation and makes problems easier to diagnose. It is not a guarantee that a search engine will include or rank every page. **A compact acceptance sheet.** Pick a service page and note its intended visitor question, preferred address and language. Confirm that the heading answers the question, the main content can be read directly and the next action is clear. Then compare the technical title, canonical address and sitemap entry with that same page identity. Repeat the exercise on an article and a package detail. This is a manageable sample for an owner and a useful complement to automated checks across all routes. Include a wrong address so the not-found behaviour is seen rather than assumed. When old content is replaced, test the particular redirect agreed for it. Keep unresolved external items in a separate part of the report. Search-console verification, domain-level redirects and crawler settings may depend on account permissions. They should neither be silently omitted nor labelled successful because the local source is ready. Accurate status reporting is part of a sound launch, particularly when the business will rely on another person to complete account setup. ## Practical checklist - Check indexable canonical pages - Inspect sitemap URLs - Verify internal links **A concrete example:** A deleted service should not return the homepage with a success status; provide an appropriate replacement or a genuine missing-page response. **A boundary to keep clear:** Do not confuse successful deployment with confirmed search indexing. ## Your next step [Tell Orvunweb about your project](/en/start-a-project/) ## Related reading - [How Google discovers a new website](/en/blog/how-google-discovers-a-new-website/) - [Sitemap, robots.txt and canonical: different jobs](/en/blog/sitemap-robots-txt-and-canonical-different-jobs/) - [Structured data for organizations, services and articles](/en/blog/structured-data-for-organizations-services-and-articles/) - [Business website service](/en/services/business-website/) - [Compare packages](/en/pricing/) ## Related services - [Business website](/en/services/business-website/) --- Locale: en Canonical: https://orvunweb.com/en/blog/a-technical-seo-checklist-for-a-new-business-site/ Updated: 2026-09-16 - [Google Search Central — SEO Starter Guide](https://developers.google.com/search/docs/fundamentals/seo-starter-guide)