Glossary
Every term in a web quote, explained plainly
184 definitions across SEO, web development, e-commerce and AI search. Each one says why the term matters, how it behaves in practice, and the mistake people make with it.
This glossary defines 184 terms across five areas: search and SEO, web development and performance, e-commerce and payments, AI search, and the contracting terms that appear in quotes. Every entry is free, ungated, and written from client work.
By subject
Search and SEO
31Crawling, indexing, structured data and the policies that decide whether a page is eligible to rank at all.
Web development and performance
29Rendering, Core Web Vitals, accessibility and the build decisions that determine what a crawler and a customer actually receive.
E-commerce and payments
20Checkout, webhooks, product data and the failure modes that only appear once a store is taking real money.
AI search and working with a developer
25AI crawlers, answer engines, and the commercial terms that appear in quotes and get nodded at rather than asked about.
Reference
38Accessibility, security, delivery and contracting terms that the other categories reference — written because the no-broken-link gate caught them missing.
Legal and compliance
19Privacy, consent, consumer rights and contracting terms — written because the legal pages reference them and because "lawful basis" deserves a definition somewhere a business owner can find it.
Domains, delivery and craft
22DNS, registrars, maintenance routines and the delivery vocabulary that appears in quotes and project plans without ever being defined.
3
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
R
S
T
U
V
W
X
Y
Why this glossary exists, and the line it stays behind
Definitional queries are real. Someone reading a quote that mentions a canonical tag, or an audit that says their site has index bloat, wants to know what that means before they reply. A page that answers it completely deserves to exist, and running a glossary is a normal content type — Cloudflare, MDN and every serious SEO tool has one.
The honest risk is that publishing many pages at once is exactly the shape Google’s scaled content abuse policy describes, and the policy applies whether a human or a machine produced the pages. So the difference is enforced in the build rather than intended in principle. Every entry must clear five gates or it is not published:
- A real definition of at least 35 words, not a restatement of the term
- At least two sections of substance beyond the definition
- A minimum word count, so nothing thin ships
- A linked guide and a linked service, so no entry is a dead end
- No orphans — every term must be reachable from at least one other term
Those gates are not decoration. They caught 38 broken cross-references and eleven entries that were too thin on their first run, and the build refused to complete until each one was fixed. The types of SEO guide covers the wider question of where the line sits.
Questions about the glossary
- Who is this glossary for?
- Business owners reading a quote or an audit and wanting to know what a term actually means, and developers wanting a second opinion on something. Every entry explains why the term matters commercially, not only what it is.
- Why publish 143 definition pages at once?
- Because "what is a canonical tag" is a real question with a real answer, and a page that answers it completely deserves to exist. The honest risk is that publishing at volume looks like scaled content abuse, so every entry has to clear gates in the build: a real definition, at least two sections of substance, a linked guide, a linked service, and no orphans. A term that cannot clear those is not published.
- Are these written by AI?
- They are written from client work, edited, and checked against gates that fail the build. The more useful question is whether each entry says something specific that you could not guess from the term — and that is a test you can apply to any page here in ten seconds.
- How is this different from Wikipedia?
- Wikipedia tells you what a thing is. These entries tell you why it matters to a business, how it behaves in practice, and the specific mistake people make with it — because that is the part that costs money.
- Can I use these definitions elsewhere?
- Quote them with attribution and a link. The code examples are free to use without attribution. See the website terms for the full position.
Want the work done rather than defined?
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