EN
BİRLİKTE KEŞFEDELİM

Web Sitesi Yayına Almadan Önce Kontrol Listesi: SEO, Form, Mobil ve Teknik Testler

Dizüstü bilgisayar mobil ön izleme kontrol listesi ve web kalite testlerini gösteren yayın öncesi çalışma masası

Finishing a website design does not automatically make the site ready to launch. A final review must cover content, interface behaviour, technical configuration, search visibility and the full contact journey. Otherwise, broken links, failed forms, incorrect canonicals, accidental indexing blocks or mobile overflow can remain unnoticed.

This checklist suits service websites, portfolios, corporate sites and campaign pages. Adapt it to the platform, and add separate tests for e-commerce, membership, booking, email or payment systems where relevant.

1. Confirm the launch scope

Record the live domain, launch window, ownership of DNS and hosting tasks, and the rollback plan. Create a page inventory covering the home page, services, about, contact, portfolio, blog and policy pages. Each item should have a clear approval state rather than an informal assumption that it is finished.

Review copy on a realistic preview, not only inside the editor. Check headings, button labels, phone and email links, dates, addresses, image descriptions and every placeholder. The visitor should understand the service and the next action without guessing. Aziz Altunkaş’s website design and development services provide context for planning the project scope.

2. Test links and URL behaviour

Try the main navigation, logo, footer, buttons, in-content links and social icons on desktop and mobile. Find links that return errors, still point to a staging domain or load an insecure HTTP resource. When URLs change, map important old pages to relevant new destinations rather than sending every retired URL to the home page.

Choose one consistent HTTPS URL format, including the preferred hostname, trailing-slash convention and letter case. Google describes redirects and rel="canonical" annotations as strong canonicalisation signals. Conflicting signals make the intended version less clear.

3. Review search metadata

Every indexable page should have a unique, accurate title and a useful meta description. Avoid repeating one generic template across the entire site or stuffing keywords into the copy. Check that each canonical points to the real preferred HTTPS URL rather than a preview, parameter or incorrect language version.

Review robots.txt and any platform-level “discourage search engines” option. Google warns that robots.txt is not a reliable method for hiding a page from search results; it primarily controls crawling. Important pages and resources should not be blocked accidentally.

Keep the XML sitemap limited to published, preferred and accessible URLs, then submit or verify it in Search Console. A sitemap supports discovery but does not guarantee indexing or ranking. Use URL Inspection after launch for the most important pages.

4. Test responsive layouts on real devices

Do more than resize a desktop browser. Open the site on a phone and test the menu, forms, sticky actions, embedded media and horizontal overflow. Include tablet and small-laptop widths. Long words, translated headings and large images often expose layout problems that are invisible in the primary design size.

Check focus visibility, contrast, alternative text and form labels as part of the final review. The website accessibility guide provides a dedicated checklist for these details.

5. Measure performance across page types

Test representative templates: the home page, a service page, an article and an image-heavy portfolio page. Large media, unused scripts, third-party tags, fonts and elements without reserved dimensions can affect real loading behaviour. The web image optimisation guide explains practical image sizing and delivery choices.

Core Web Vitals currently cover loading with LCP, responsiveness with INP and visual stability with CLS. Google’s web.dev guidance recommends assessing the 75th percentile of page loads and separating mobile from desktop. Lab tests are useful for diagnosis, while field data reflects real visits; one score cannot prove that every user receives the same experience.

6. Test forms from start to finish

For contact, quote, newsletter or account forms, test empty required fields, invalid email addresses, long messages and mobile input. Error feedback should identify the field and explain how to correct it. A successful submission should show a clear confirmation, and the message must reach the intended destination.

Client-side validation improves immediate feedback but is not a substitute for server-side validation. MDN also notes that submitting from a secure page to an insecure HTTP endpoint can trigger a browser warning because the data is not encrypted. Check delivery, spam filtering and any automated reply with controlled test submissions.

7. Verify measurement and third-party tools

If analytics or advertising tags are present, confirm that they send data to the intended property and that test traffic can be recognised. Review cookie preferences, privacy text and the behaviour of maps, videos, chat tools or social embeds. A tag appearing in the source does not by itself prove that complete data is being collected.

8. Prepare backup, rollback and handover

Take a fresh file and database backup before launch, and record where it is stored and who can restore it. For theme, plugin, server or domain changes, document the path back to the last working version. A backup is only useful when access and recovery responsibility are clear.

The handover should cover the domain, hosting, administration, licences, fonts, form recipients, measurement identifiers, maintenance scope and renewal dates. Use a secure password manager and appropriate access levels instead of placing credentials in ordinary email or shared notes.

Post-launch essentials

  • Critical pages return successful HTTPS responses.
  • Navigation, buttons and contact links reach the correct destination.
  • Titles, descriptions and canonicals match each page.
  • Robots rules do not block important content or resources.
  • The sitemap is current and accessible.
  • Mobile menus, forms and embedded content work on a real device.
  • Images load at suitable sizes without avoidable layout shifts.
  • Form submissions reach the correct recipient.
  • Measurement tools use the intended account.
  • Backup and rollback responsibilities are documented.

Launching is the beginning of a monitored period, not the end of the project. Recheck critical pages during the first hours, then watch form delivery, error logs, Search Console notices and real-user behaviour. To discuss the scope and launch plan for a website project, use the contact page.

Share This Article:
Aziz Altunkaş
Aziz Altunkaş

With over 8 years of experience, I support brands with graphic design, social media, web design and digital advertising. Contact me on +90 542 820 41 94 or at iletisim@azizaltunkas.com.tr to discuss your project.

Leave a Reply

Your email address will not be published. Required fields are marked *