Start with a service customers can understand
Imagine a Budapest curtain workshop launching a website for alterations and made-to-measure curtains. Give each proposed page a specific customer question: can existing curtains be shortened, or does the customer need a new set? Ask the owner to approve the service details, the area served and the next step before reviewing decorative copy.
Google recommends clear, distinctive page titles and useful content. A small set of complete service pages can be a better first delivery than many unfinished pages. Separate services when their explanations differ; every extra page creates another piece of information the business must maintain.
Test the addresses customers will actually open
Google requires crawler access, a successful page response and indexable content; eligibility does not guarantee indexing. Ask the developer to inspect the final public pages for leftover launch restrictions and use Search Console URL Inspection for specific addresses.
For the workshop, open the alterations page from the live homepage and send its address to a colleague using another device. Can that person understand the offer without an explanation? Record the exact address and result. Keep private customer documents and staff pages outside this public launch review; making a service page discoverable does not require opening everything.
Agree which address represents each page
Google uses canonical signals to choose among duplicate pages. Redirects, canonical declarations and sitemap entries should express a consistent preference, although Google ultimately chooses. Have the developer demonstrate that agreement for the launch pages.
The workshop owner can keep a simple list linking each approved service to its preferred public address. Compare that list with links in the menu and campaign drafts. If an old alterations page has a replacement, agree where its visitors should arrive. Ask for an explanation before approving a blanket redirect that sends every old page to the homepage.
Treat the sitemap as a handover item
A sitemap helps Google discover URLs; it does not promise that they will be crawled or indexed. For the workshop, ask the team to reconcile the sitemap with the approved page list and explain any intentional differences.
Agree who owns Search Console access and who investigates an unexpected result. Keep publication, indexing observations and actual enquiries as separate entries in the launch record. That prevents a successful technical release from being described as proven business growth. Schedule a follow-up review with a named owner instead of promising a search position or a fixed discovery date.
Use this checklist at the launch review
Ask for a short evidence sheet covering the actual published site. It should let the owner and developer revisit the same pages without reconstructing decisions from a long message thread.
- Approve each service page against a real customer question and its contact route.
- Record the final public address and the result of its access check.
- Confirm that the preferred addresses agree across the launch configuration.
- Compare the sitemap with the approved list and document exceptions.
- Assign Search Console access, follow-up work and responsibility for content changes.