Most agencies treat search, speed and accessibility as a clean-up job after launch. We put them in the build rules instead, because retrofitting is slower and the fixes are always partial. Here is what that looks like on a site for DiscoverMSPs, a provider-intelligence business that sells a data subscription to technical and commercial buyers.\
The constraint: the page replaces a sales call
A data subscription gets bought after reading. That means the site carries explanation, proof and signup. If a page is slow on a mid-range phone, or the heading structure is a mess, the explanation never lands. So we treat these as engineering constraints, not design preferences.
Rule 1: write the head and the markup with the page
Titles, meta descriptions, headings and structured data are written as each template is built. Organisation and breadcrumb markup lives in the templates, not in a plugin added later. A new page then inherits correct markup instead of needing someone to remember it\
Rule 2: a performance budget that is set on day one
We set a weight and speed target at the start and enforce it during the build. Images, fonts and third-party scripts are the usual offenders, so they are held to the budget as they are added rather than trimmed at the end. The target is Core Web Vitals in the "good" band on a mid-range phone, not on a developer laptop.
Rule 3: accessibility checked before launch
We test against WCAG 2.2 level AA: contrast, keyboard operation, focus order, form labels and alt text. A subscription form that a keyboard user cannot finish is a lost sale, and an easy one to prevent.
Rule 4: forms that match the law
The enquiry forms follow India's Digital Personal Data Protection Act, 2023: say what is collected, show the notice, and record marketing consent separately from the enquiry itself. We are not lawyers, so we confirm final wording with the client.
Rule 5: hand the keys over
Code, hosting, domain and every third-party account go to the client in their own name, with a walkthrough. It removes a dependency that some agencies leave in place.
A checklist you can reuse
- Are the title and meta description written with the page, not after?
- Does the page meet your budget on a real phone?
- Can you finish the main form with a keyboard only?
- Does the form say what happens to the data?
- Does the client own every account?
See the finished build
If you want to see the result and the method in full, the Tech Conversion case study walks through it.
About The Author: Mohammed Imran is the founder and growth strategist of Tech Conversion, a digital marketing and web development agency working with businesses in India, the UAE, the US and the UK. His work focuses on how people search today, in Google and in AI assistants, and on what makes a business the answer they find. He researches SEO, AEO and GEO, and writes about growth strategy that turns search visibility into real enquiries and sales.
Comments
Join the discussionNo comments yet. Be the first to comment.