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

18
How to check if AI crawlers can reach your site Fetch your home page with each AI crawler user-agent and read the status code. Every line should return 200. A 403 means an e… 6 steps → How to check what a crawler actually sees on your page View the page source rather than the Elements panel, and count the words. DevTools shows the DOM after JavaScript has run; vi… 5 steps → How to submit a sitemap to Google Verify your site in Search Console, open Sitemaps in the left menu, enter the sitemap path and submit. The sitemap must conta… 7 steps → How to verify Search Console by DNS Add a TXT record to your domain’s DNS with the value Google provides, then confirm in Search Console. DNS verification surviv… 7 steps → How to find orphan pages on your site Crawl your site starting from the home page, list every URL the crawl reached, and compare that against your sitemap. Anythin… 6 steps → How to audit your internal links Crawl the site, count inbound internal links per page, and compare that against which pages you actually want to rank. Most s… 7 steps → How to fix a noindex tag left in production Remove the noindex, confirm it is gone from the live HTML rather than only from your source, then request indexing in Search … 7 steps → How to set up redirects for a site migration Crawl every URL currently returning 200, map each to its closest equivalent on the new site, and deploy them as single-hop 30… 8 steps → How to move a site from HTTP to HTTPS Install a certificate, fix every mixed-content reference, redirect all HTTP URLs to HTTPS in one hop, update canonicals and s… 7 steps → How to add structured data to a page Write a JSON-LD block describing what the page is, put it in a script tag, link the nodes with @id references, and validate w… 7 steps → How to add FAQ schema correctly Publish the questions and answers visibly on the page first, then mark them up as a FAQPage with matching text. Expect no Goo… 6 steps → How to set up Bing Webmaster Tools Sign in at bing.com/webmasters and import your verified properties from Google Search Console — it takes about two minutes an… 6 steps → How to create an XML sitemap Generate it from your build or CMS rather than writing it by hand, include only canonical indexable URLs that return 200, spl… 7 steps → How to write a robots.txt file Put it at the root of the domain, allow everything you want crawled, disallow only paths that genuinely should not be request… 7 steps → How to add hreflang tags correctly Add a link rel="alternate" hreflang element for every language or regional variant, including a self-reference, on every page… 7 steps → How to add breadcrumbs to a website Render a visible breadcrumb trail in a nav element with an ordered list, mark the current page with aria-current, and emit ma… 7 steps → How to recover from a search traffic drop Establish when it started and whether it is technical, algorithmic or seasonal before changing anything. Check for manual act… 7 steps → How to handle a Google manual action Read the notice in Search Console to see exactly what was flagged, fix the underlying cause completely rather than partially,… 7 steps →

Content

7

Local SEO

4

Ownership

3

Performance

5

Accessibility

4

Build

7

Security

2

Hiring

3

E-commerce

2

Maintenance

2

Process

2

What 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
WhatsApp — opens a chat with +92 346 5348466 in a new tab