A launch can look finished while the first enquiry disappears into the wrong inbox. This guide is for the person who has to say whether the website is ready—and then own what happens next.
For the wider planning context, start with the business website planning guide.
THE SHORT ANSWER
A launch decision you can defend
Launch the journeys you can show working. Broken contact routes, misleading claims and missing owners block launch. Cosmetic fixes can wait for a later list.
- Check whole visitor tasks, not just how each page looks.
- Distinguish a feature that renders from a journey that has been tested through to its actual result.
- Write down unfinished work and its owner. A nice-looking home page does not mean the launch is done.
- Before handover ends, agree who owns access, backups, support and content.
- 01Follow the journeyOpen , understand , act
- 02Verify the handoffSubmit , receive , respond
- 03Name the ownerRecover , maintain , improve
Rule of thumbA working page is only part of a working website.
Planning framework and researched guide. Sources reviewed 18–19 November 2026. Prices keep their own check dates. We have not run a hands-on product trial or measured a business result. Our advice is based on the stated task and official docs. Read the evidence standards.
40 checks before launch, on launch day and in week one
Use the list as a sign-off sheet. A check is done only when its proof exists. Launch blockers include broken forms, lost ownership, wrong redirects and exposed private data.
| Stage | Check | What to verify |
|---|---|---|
| Before launch | Domain ownership and renewal | Confirm the business controls the registrar account and recovery address. |
| Before launch | DNS and TTL | Record existing A, AAAA, CNAME and MX records. Plan the cutover and email impact; do not delete unrelated records. |
| Before launch | TLS certificate | Open the site over HTTPS and confirm the certificate covers every hostname used. |
| Before launch | HTTP and hostname redirects | Choose the preferred HTTPS hostname. Confirm the alternate host and HTTP route redirect to it without a chain. |
| Before launch | Permalinks and old URLs | Keep existing slugs unless a change is needed. Add a direct 301 for each changed URL. |
| Before launch | Launch indexing decision | Record who can remove a pre-launch noindex setting, and check every page template straight after it is removed. |
| Before launch | Robots access | Keep intended public pages crawlable so crawlers can read their meta robots directives. |
| Before launch | Canonicals | Check homepage, a service page, an article and a category in rendered page source. |
| Before launch | Sitemap | Check eligible canonical URLs and remove redirects or obsolete routes from the submitted sitemap. |
| Before launch | Titles and descriptions | Give each important page a useful title and a distinct, accurate description. |
| Before launch | Structured data | Check the actual page, author, organisation and breadcrumb relationships. |
| Before launch | Social previews | Open a relevant image with the intended crop and sufficient text contrast. |
| Before launch | Navigation | Follow every header and footer link; check dropdowns with a keyboard. |
| Before launch | 404 page | Request a made-up URL. It should return 404 and help the visitor recover. |
| Before launch | Favicon | Check browser tab and touch-icon settings. |
| Before launch | Images and alt text | Use appropriate dimensions and formats. Describe informative images; leave decorative alt text empty. |
| Before launch | Mobile layout | Check narrow screens, long headings, wide tables and touch targets. |
| Before launch | Keyboard and focus | Reach menus, links, forms and dialogs without a mouse. |
| Before launch | Form validation | Submit empty, invalid and valid test cases using authorised test details. |
| Before launch | Submission storage | Confirm a genuine reference is stored. A success message alone is not evidence of delivery. |
| Before launch | Notification delivery | Check the intended inbox and reply route; record what was actually received. |
| Before launch | Downloads | Open each file and check HTTP status, MIME type, filename and real contents. |
| Before launch | Search | Try a known article, a misspelling and a query with no result. |
| Before launch | Privacy and consent | Match the notice and consent choices to the services actually running. |
| Before launch | Backups | Take a current database and file backup and record where it is stored. |
| Before launch | Restore plan | Confirm who can restore and how; a successful backup is not a successful restore test. |
| Before launch | Ownership handover | Record hosting, domain, analytics, email and maintenance owners. |
| Before launch | Performance baseline | Save a dated mobile and desktop report with the URL and test conditions. |
| Launch day | DNS resolution | Check the live hostname resolves to the intended service. |
| Launch day | Public journeys | Repeat the main contact, purchase or subscription journey on the live domain. |
| Launch day | Search Console verification | Verify the correct property using a method the owner controls. |
| Launch day | Sitemap submission | Submit the canonical sitemap after the owner authorises indexing. |
| Launch day | Analytics collection | Use DebugView or equivalent to confirm authorised test events and consent behaviour. |
| Launch day | Monitoring | Set up an authorised uptime check and a named response owner. |
| Launch day | Caching | Purge changed pages and confirm logged-out visitors see the correct version. |
| First seven days | Broken-link review | Review server logs and crawl results for missing destinations. |
| First seven days | Indexing review | Inspect a sample of key URLs; submission does not guarantee indexing. |
| First seven days | Search and form issues | Review genuine enquiries and error reports before adding features. |
| First seven days | Backup schedule | Confirm the next scheduled backup completed. |
| First seven days | Change log | Record fixes, owner and next review date. |
Technical references: HTTPS for WordPress, Google’s redirect guidance, noindex controls and WordPress backups. This is a launch checklist for readers. TechVendorly itself stays hidden from search until its owner approves launch.
Define the journeys the site must support
List the main tasks: understand the offer, find a service or article, contact the business, subscribe, purchase where relevant, or download a resource. Give each a starting point and an expected outcome.
Use the business website planning guide to plan the wider project. The homepage checklist covers the first page; this review covers the rest of the site.
Check content, identity, and claims
- Each important page has a clear purpose and a useful next step.
- Named people show real names, relevant bios and real photos where you have them.
- Product details, service commitments, prices, and statistics have been verified.
- Constructed examples and illustrative figures are labelled.
- Sponsored and affiliate relationships are disclosed where they apply.
Look for old demo content, placeholder contact details, awards you cannot back up and repeated generic text. A site can look polished and still show details that do not belong to the business.
For a publication, check author names, dates, sources, the editorial policy and the line between guides and hands-on reviews. Do not add “reviewed by” unless a second person really did the review.
Follow navigation and internal links
Open every main menu and footer link. Follow cards, in-text links, downloads and the main button on each key page. Check that each link lands where the reader expects.
When URLs change, test old addresses as well as new ones. Confirm that a redirect reaches the final destination without unnecessary hops. Update internal links so they point directly to the new address.
A crawl can help identify technical failures, but it does not know whether a destination is useful. Pair it with a human review of the main visitor tasks.
Review mobile and keyboard use
Check the navigation, reading order, touch targets, buttons, forms, image crops, and wide tables on a narrow screen. A desktop screenshot scaled down is not the same as a responsive review.
Use only a keyboard to reach the menu, search, contents links, accordions, form fields and main buttons. Check that focus stays visible and controls have clear labels. Note problems; a theme component is not accessible just because it came with the theme.
Test forms beyond their fields
Check visible labels, required fields, input types, privacy notes and feedback messages. Then send approved test details and confirm the entry is saved, delivered and acknowledged. A form that shows on screen has not passed this second step.
Check who owns the inbox and who reads the entries. If it sends to a domain address, confirm that inbox or forward really exists. Keep a private note of delivery work still open.
For newsletters, verify the form, confirmation email, and welcome route. Do not create plans using someone else’s address or describe the journey as tested when only the signup screen has been viewed.
Open each downloadable resource
Download the file and open it. Check the headings, instructions, any formulas and that it opens in a normal app. A working link is only the first check.
For a spreadsheet, change a realistic input and confirm the totals update. Reset the template before you publish it. For a document or PDF, check the pages for cut-off text, odd breaks and unreadable text.
Our free resources are planning aids. Their examples and assumptions should be checked and adapted to the reader’s own work.
Check metadata and connected services
Check the page title, description, canonical URL, share image and structured data on real pages. The author and details shown should match the metadata. Remove personal details that should not be public.
Only mark analytics done when the service is connected and you have seen the event arrive. Installing a plugin does not prove visits or form events are recorded. Keep privacy and consent settings in line with the services you use.
Confirm operations and handover
Identify the owners of the domain, hosting, website access, backups, updates, and content review. Confirm the recovery route and where support comes from. An installed tool is not proof that a usable backup exists.
Keep a short running note of key duties and open work. Do not leave the business relying on a personal login nobody has written down, or a service nobody knows how to manage.
Record the launch decision honestly
| Area | Useful evidence | If it is not complete |
|---|---|---|
| Links | Crawl and completed visitor journeys | Record the failing destination and owner |
| Forms | Stored submission and verified delivery | Keep delivery marked unverified |
| Newsletter | Confirmed signup and received messages | Do not claim end-to-end verification |
| Performance | Dated measurements and test conditions | Report the measurement limit |
| Operations | Confirmed access, backup, and support | Assign the remaining work |
You can launch with known limits if they are written down and acceptable for the site. The checklist should make those limits clear, not pretend every test has passed.
Prepare a recovery route before promoting the site
WordPress’s backup docs separate the database from the files. Note what the backup includes, where it is kept, who can reach it and what would trigger a restore. Having a backup file is not the same as a tested restore.
Name a contact for the domain, hosting, billing, updates and content. Explain how an urgent correction reaches the right person. If an outside service runs a key journey, note its support route and the manual fallback when it is down.
Launch evidence should describe what happened. “Test message received in the agreed inbox” is useful when observed. “All forms work perfectly” is too broad for one test.
Tools to consider
Research shortlist, not tested reviews. These are tools to look into, not endorsements or a ranking. We checked prices and plan limits on the linked official pages on 16 November 2026. Recheck the current quote, taxes, renewal terms and availability before you buy.
Check publishing, the shop and payments as separate launch items. Having access to the software does not prove the whole journey works.
| Tool | What it is for here | Who it may suit | Starting price and conditions |
|---|---|---|---|
| WordPress.org | Check publishing, updates, backups and ownership on a self-hosted site. | A service business or publisher with a named technical maintainer. | ₹0 for the open-source software. Domain, hosting, support and any paid extensions are separate. Official pricing / plan details Price checked on 16 November 2026. |
| WooCommerce | Prepare store checks for products, tax settings, orders and extension dependencies. | A WordPress merchant that can maintain its ecommerce setup. | ₹0 for the core plugin. Hosting, payment processing, development and optional extensions are separate. Official pricing / plan details Price checked on 16 November 2026. |
| Shopify Basic | Prepare catalogue, domain and checkout checks on a managed store. | An Indian retailer planning platform, app and external payment costs. | ₹1,499/month equivalent billed yearly (₹17,988/year), or ₹1,994/month billed monthly. Check tax, apps and third-party payment fees separately. Official pricing / plan details Price checked on 16 November 2026. |
| Razorpay Payment Gateway | Check onboarding status, integration mode and a documented payment test plan. | A merchant preparing authorised sandbox checks before any real payment. | ₹0 setup and annual maintenance; standard successful payments: 2% platform fee + GST on that fee. Some payment methods have different rates. Official pricing / plan details Price checked on 16 November 2026. |
Use sandbox or dummy records while you test. Record what actually happened and what is still open. Never say payments or emails work just because the fields appear.
Continue with the related guides
- How to plan a business website that helps visitors act
- Homepage checklist: 20 elements for a clearer business website
- Small business SEO: a practical planning playbook
- WordPress Hosting in India: Prices and Buying Checks
- Google Search Console for Beginners: Reports to Decisions
Questions before launch
Is a visual review enough?
No. Follow the important actions and check the connected services behind them.
Should I test old URLs after a redesign?
Yes. Check that renamed addresses reach the right final page, and update your internal links.
Can I say a form works when it renders?
Say that it appears on the page. Delivery and the confirmation need their own checks with approved test details.
What belongs in the handover?
Who owns access, the support routes, who handles backups and updates, content reviews and open work.
Can I launch with a few unresolved issues?
Sort issues by impact. A small visual glitch can go on a later list. A broken main enquiry route, a wrong offer or no recovery owner needs a decision before the site goes live. Note the issue, its effect, the owner and the agreed fix. A staged launch only helps if the released journeys are truly ready.
What should a visitor see after submitting a form?
Confirm the action clearly and explain what happens next, without promising a reply time the team has not agreed. Make errors easy to understand and fix. The W3C form-notification guidance is a useful reference. Check delivery separately: a success message on screen does not prove the right person got the entry.
Sources and further reading
- WordPress Theme Handbook: UI best practices.
- WordPress: alternative text for images.
- Google Search Central: SEO Starter Guide.
- WordPress.org: official plan and pricing information (checked 16 November 2026).
- WooCommerce: official plan and pricing information (checked 16 November 2026).
- Shopify Basic: official plan and pricing information (checked 16 November 2026).
- Razorpay Payment Gateway: official plan and pricing information (checked 16 November 2026).
Last updated: 22 November 2026. Individual prices retain their stated check dates.




