SEO checks before launching a website

Start with the checks that affect customers

A pre-launch SEO review should begin with important service and enquiry pages. First confirm they load and work; then inspect search signals and editorial quality. A long report is not useful if customers cannot submit a form or a core page is accidentally excluded from search.

Do not test only the homepage. Review a representative page of each type: service, case study, article, category, product and contact page. A template issue can repeat across an entire section.

Check crawling, indexing and URLs

Open your key pages in a normal browser session. Make sure they are publicly accessible and not carrying a noindex directive intended for staging. Robots.txt controls crawling; noindex controls appearance in search results. Blocking crawling is not a dependable substitute for noindex, because a search engine can discover a URL through a link without reading its content.

1. Confirm the expected URL loads and returns the correct page.
2. Read robots.txt for unintended restrictions on services, products or articles.
3. Inspect page HTML for noindex and unexpected canonical URLs.
4. Check that the sitemap lists current preferred addresses.
5. Use search console URL inspection after launch for important pages.

If URLs change during a redesign, map old addresses to the new ones and implement redirects. Update internal links rather than relying on redirects forever. A self-referencing canonical can help indicate the chosen page, but it does not replace a redirect when a page has moved.

Make each page useful for its search intent

SEO begins with the customer's question, not a spreadsheet of keywords. A commercial page should make the offer understandable: what is included, how the work proceeds, how pricing is determined, what limitations apply and what the visitor should do next. An article should answer a real question with clear criteria, examples and sources for technical claims.

Read each page and ask how it differs from the next. Two near-identical pages targeting slightly different wordings are unlikely to help users. Clarify their roles or combine them into a more complete resource. Avoid creating empty location pages without market-specific information.

• Use one H1 that names the page topic clearly.
• Write subheadings that reflect the actual structure of the answer.
• Explain the service in plain language and describe its boundaries.
• Use descriptive internal links to relevant next steps.
• Match the CTA to the visitor's stage: learn, request a quote or discuss a project.

For example, a page about SEO services should state the scope and process, while a technical article can explain how to assess a specific issue before commissioning work.

Review the multilingual experience

Each language version needs its own URL and complete, useful content for its audience. Translating one heading while leaving navigation or forms in another language creates a poor experience. Check the HTML language attribute, menus, enquiry fields, currency and market-specific terms.

Hreflang can identify corresponding language versions. For each pair, confirm that both pages point to each other and each has an appropriate canonical URL in its own language. Do not connect pages simply because their paths look similar; their main topics and purpose should genuinely match.

If the European offer differs from the Moldovan one, localise service terms, examples and commercial details. A literal translation is not the same as a page written for a different market.

Test images, mobile layout and speed

Use a real narrow-screen viewport to review text, menus, forms, tables and buttons. A page can look polished on desktop yet make a simple enquiry difficult on a phone. Large image files also add waiting time without improving the decision. Export images near their display dimensions, choose an appropriate format and lazy-load images below the first screen when suitable.

Write concise alt text for images that carry meaning; decorative images do not need keyword-stuffed descriptions. After optimisation, inspect the page again. Speed work should not hide important content, damage image quality unnecessarily or break interactions.

Monitor the launch rather than stopping at publication

Once the site is live, check that search engines can discover important pages and analytics records meaningful enquiries. Early data tells you mainly about technical health: crawling errors, excluded URLs, broken forms and unexpected traffic sources. It cannot prove SEO success after a few days.

1. Review indexing reports and the reasons important pages are excluded.
2. Watch visits to key service pages alongside qualified enquiries, not traffic alone.
3. Refresh outdated prices, conditions, examples and internal links.
4. When URLs change, monitor redirects and 404 errors.
5. Analyse languages, markets and page types separately.

A checklist creates the foundation. Search performance then depends on competition, answer quality, trust and continued improvement. If ongoing fixes are needed, website support should have a clear owner and priorities.

Frequently asked questions

Are Title and Description tags enough?

No. Metadata can help describe the page but cannot replace accessibility, useful content, sound structure and a working customer journey.

Should every page be submitted manually for indexing?

URL inspection helps diagnose important pages, but it does not replace internal links or a sitemap. A submission request is not a guarantee of indexing.

Should SEO be reviewed before or after launch?

Plan content, URLs and settings before publication, then inspect real crawling and measurement after launch. Both stages matter.

For technical rules, consult Google Search Central on robots.txt, canonicals and localised versions.