Pre-launch website QA services
Get a review of the version your team plans to launch. We check the agreed pages, content and visitor actions on staging and record issues your developer can work through.
Global · English Россия · Русский
Agree what your website needs before development starts. We plan the sections and pages and document what visitors should find and be able to do.
Get a review of the version your team plans to launch. We check the agreed pages, content and visitor actions on staging and record issues your developer can work through.
Move the agreed content, map changed URLs and check pages and redirects after launch.
We build WordPress service websites and product catalogs. Agree on the pages, features and editing setup, then review the site before launch.
Get a sitemap showing proposed sections, page types and how they fit together.
Describe what information each agreed page type needs, what visitors should be able to do and which functions support those actions.
Document agreed requirements for navigation, search, forms, mobile display and content management in a specification for your developer.
Discuss what you sell, who uses the site and how they should get in touch.
Decide how visitors should move between sections and what the key page types need to cover.
Record the agreed structure, separate required and optional features and flag decisions for the build.
The sitemap is a plan of the website’s pages. It shows which sections sit at the top of the structure, which pages belong under them and where visitors should be able to move next. A site for a service business may need a page for each service and a clear route to an enquiry. A product catalogue needs a different plan for browsing categories, finding products and asking about an item.
We start with the information customers need to make a decision. That helps settle questions such as whether two offers belong on one page, which details deserve their own page and when a site search would help. If a project also needs keyword research or briefs for individual pages, we scope that work separately.

The specification gives a designer or developer something concrete to work from. It describes the required content and functions of the agreed page types. A service page, for example, may need space to explain the offer, state its conditions and give visitors a way to enquire. The document can then set out what the form needs to collect and how visitors should reach it.
We record which materials are ready and which your team still needs to supply or approve. Product details, legal wording and other information that needs a decision stay marked for review. We also distinguish features you need for the first build from ideas you may want to consider later, so developers can estimate the agreed scope.

Use the sitemap and specification to brief your chosen developer and review proposals against the same requirements. Design, development and content production are scoped separately. If you are planning a rebuild, share the existing website and tell us which offers or sections are changing.
Yes. We review the current pages and materials, then propose a structure based on what the website needs to do after the rebuild.
Send any existing pages and materials, a description of your products or services and the actions you want visitors to take. We can identify missing inputs as we agree the scope.
Yes. The sitemap and specification are designed to help you explain the project and agree the build scope with the developer you choose.
Share your site and what you want to improve. We can suggest a starting point and explain what the work would involve.