How-to
Step-by-step procedures for the jobs a website actually needs
64 procedures across technical SEO, performance, accessibility, security, legal pages and hiring. Each states what you need first, what each step accomplishes, and how to check it worked.
These 64 pages are ordered procedures, not explanations. Each one lists what you need before starting, gives numbered steps with the outcome of each, and ends by telling you how to verify the change actually took effect on the live site.
Technical SEO
18Local SEO
4Ownership
3Performance
5Accessibility
4Build
7Security
2Legal
4Hiring
3E-commerce
2Maintenance
2AI search
1Process
2What makes something a how-to here
A genuine ordered procedure, with at least four steps, where each step is an action and a stated outcome. That is a build rule rather than an editorial preference — a subject that cannot be written that way fails the build and becomes a guide or a glossary entry instead.
The reason is that HowTo structured data describes a procedure. Wrapping it
around a list of benefits is a structured-data violation and a common one, so the constraint
is enforced where it cannot be forgotten.
Questions about these procedures
- Are these written for beginners or developers?
- For whoever has to do the job. Each one states what you need before starting and what each step accomplishes, so a business owner can follow the ones that need no code and a developer can skim to the command. Nothing assumes you already know the answer.
- Why do some of these tell me the fix is not available?
- Because sometimes it is not. The AI crawler procedure ends by saying that on most shared hosting the block is the provider’s rule and cannot be fixed from your account. A procedure that pretends otherwise wastes your afternoon.
- Do you use these yourself?
- These are the routines I run on client work, written down rather than invented for the page. Where a step exists because I got something wrong once — measuring contrast, retrying link checks — the page says so.
Want one of these done for you instead?
Send the brief and you get a reply within one business day — either questions, or a scoping call. If your project is not something I should take on, I will say so then.
- Response
- Replies within 1 business day
- Hours
- Mon–Fri, 09:00–18:00 PKT — overlaps 05:00–14:00 UK, 00:00–09:00 US Eastern
- Booking
- Booking projects from October 2026