A website that displays is not necessarily ready for customers. Before launching a website in Agadir, check the content, actions and information sent to your team. Acceptance means comparing the delivered version with agreed needs, using concrete situations rather than visual impressions alone.
Agree on an acceptance checklist
Review the scope: pages, languages, forms and functions included. For each item, record the expected result and who approves it. Distinguish a defect against the agreed scope from a new request needing a separate decision.
Use an identifiable version for review and keep feedback together. A correction should be traceable and then checked. Our guide to website creation timelines helps place this stage in the schedule rather than leaving it to the final hours.
Review content and follow links
Check actual services, contact details, hours and conditions. Open navigation links, buttons, files and pages mentioned in the text. Remove temporary content and make sure visuals match the offer presented.
For each language, follow a visitor’s route: menu, detail and contact. Language switching should reach the corresponding page where available. Assign reviewers and approve commercial details before calling the version ready.
Test forms through to delivery
Submit a complete enquiry, try a missing field and correct it. Check that messages clearly explain the error or outcome. An on-screen success message should reflect actual behaviour; also verify delivery to the intended recipient.
Compare the received message with submitted details and check that the team can reply. Our guide to improving website quote requests complements this journey. For calls, email links or WhatsApp, check destinations without confusing a click with a conversation that actually happened.
Check mobile use and interactions
Try representative widths and a phone where possible. Inspect text, images, menus and forms. Fixed elements should not hide information or controls. Also check long pages and content that differs between languages.
Move through actions using a keyboard and record observed barriers. Our website accessibility guide helps scope these checks. This initial pass is not a complete conformance evaluation; agree on the level of review actually included.
Verify search visibility settings
For pages intended for search, check that preparation restrictions do not unintentionally prevent indexing. Private and test pages should not become public automatically. Review titles, descriptions and preferred page addresses in the final version.
The sitemap should contain the selected public URLs, with addresses consistent with the pages. Submission does not guarantee immediate indexing or rankings. After launch, Search Console URL inspection can help check what Google can access.
Organize launch and handover
Confirm the version to publish, available contacts and checks to repeat at the public address. When replacing a website, prepare the old URLs and planned redirects before switching. Define what to do if an essential function stops working.
Hand over authorized access, editing guidance and a way to report incidents. Specify who handles enquiries from launch day. Our website maintenance guide helps distinguish delivery checks from recurring work and support after publication.
What to prepare for final acceptance
- Scope and reference version for approval.
- Content reviewers for each language.
- Contact scenarios with delivery checks.
- Pages, devices and interactions to examine.
- Responsibility for launch, handover and incidents.
What should the launch budget include?
The quote should specify included checks and scope limits. Separate review, fixes, post-publication checks and recurring follow-up. Page and language counts affect the work.
Accepting the delivered version
Agreed pages, content and journeys, feedback collection and fix verification. Specify languages and approval owners.
Publishing and checking
Planned launch, public checks, access handover and defined assistance. Identify migrations and external tools requiring separate work.
To scope your launch, contact Web Agadir with the website scope and essential visitor actions. These details help prepare concrete acceptance checks before publishing.
Common questions before a website launch
Is a website ready when its build passes?
Not necessarily. A build checks part of the technical setup, but does not confirm content accuracy, enquiry delivery or every real journey.
Should every language be tested?
Yes. Content, links and layouts can differ. Plan reviews and important scenarios in each published version.
Is a form confirmation enough?
No. Also check the details received by the team and the ability to reply. The displayed message and delivery are separate checks.
Does a sitemap guarantee Google visibility?
No. It helps communicate URLs without guaranteeing indexing or position. Check settings and monitor available Search Console information.
Should checks be repeated after publication?
Yes, for important functions. Verify the public version and follow up when content or tools change.