AtlasWeb Works Blog

Start with the pages a customer needs to make a decision: what you do, where you work, what a service includes, and how to request a quote. SEO helps search engines interpret those pages; it does not guarantee rankings, enquiries, or sales.

1. Match pages to real services. List the questions customers ask before booking, then write clear answers on the relevant service page. Use a location only if you actually serve it. Avoid copying the same page for places where you do not operate.

2. Write descriptive titles. Give each page a distinct title that identifies its service or topic. A useful description can summarise the page, but search engines may choose another snippet. Do not repeat a string of keywords.

3. Check the mobile experience. On a small screen, read the main content, open the menu, tap the telephone link, and complete the enquiry form. Look for overlapping text, small tap targets, or errors that prevent submission.

4. Explain scope and limitations. Describe what is included, what information is needed for a quote, and what affects pricing. If a price is only an estimate, say so. Publish examples or customer feedback only with permission and supporting records.

5. Maintain accurate business information. If your business is eligible for a Google Business Profile, keep the service area, opening hours, website, and contact details current. Do not invent an office address or publish reviews you cannot substantiate.

6. Check links and page access. Follow the links from your homepage to each service and contact page. Fix broken destinations. A sitemap can help discovery, but it does not force indexing. Keep private account and checkout pages out of the public sitemap.

7. Make images and structure useful. Resize large images, add descriptive alternative text where an image conveys information, and use headings to organise the page. Decorative images should not add unnecessary narration for screen-reader users.

8. Measure loading and usability. Use browser developer tools or PageSpeed Insights to identify large downloads and layout movement. Test actual customer journeys as well as automated scores; a high score alone does not establish that a form works.

9. Keep structured data truthful. Markup should describe information visible on the page. Leave out ratings, awards, and reviews unless they are genuine, permitted, and appropriate for the markup type. Structured data does not guarantee enhanced search results.

10. Review evidence rather than promises. Search Console can show indexing issues and search queries. Where analytics is enabled with appropriate consent, compare enquiries with visits and record the period measured. Traffic changes alone do not establish that SEO caused additional sales.

Prioritise issues that stop customers from finding essential information or contacting you. Search visibility depends on competition, relevance, indexing, and other factors outside a website provider's control. There is no fixed timetable for a ranking improvement.

A useful website brief starts with the decisions visitors need to make, not with a theme or a page count. Gather the information below before requesting a quote so you can compare proposals on the same basis.

Define the main customer action. Decide whether visitors should call, request an estimate, book an appointment, or buy a product. Identify the details needed for that action. An enquiry form may need a service choice and location; it should not collect sensitive information unnecessarily.

Prepare your service information. For each service, list what is included, exclusions, the area covered, and the next step. State whether prices are fixed or subject to a quote. Do not promise response times or availability unless you can maintain them.

Check rights and evidence. Supply photographs you own or have permission to use. Get consent before publishing identifiable customers, testimonials, or project details. Keep evidence for any claimed result and explain how it was measured. If evidence is missing, describe the work rather than inventing a success story.

Agree on ownership and access. Ask who controls the domain, hosting, source files, and content accounts. Confirm what you receive at handover, how renewals work, and how you could move to another provider. Separate one-off development costs from ongoing charges.

Specify form handling. Agree where submissions go, who can access them, and how long they are retained. Test successful submission, required-field errors, and failure messages. A success message is not enough: check that the recipient actually receives the enquiry.

Plan privacy and measurement. Identify which cookies and third-party services the site uses. Explain data handling in the relevant notices and check applicable consent requirements before enabling analytics or advertising. Collect only what you need to answer the enquiry.

Define launch acceptance checks. Verify links, telephone and email actions, keyboard navigation, readable mobile layouts, image descriptions, HTTPS, and page titles. For a shop, also verify prices, payment failures, delivery information, and refunds. Write down who signs off each check.

Agree on maintenance. Decide who updates opening hours, services, prices, software, and backups. Ask how restoration is tested and how to report a problem. A website needs ongoing attention; launch does not end that responsibility.

Assess cost against your own business figures. Use actual project costs, ongoing charges, and the value of enquiries that become paying customers. A website can make information and contact options available, but it does not guarantee demand or a return on investment.