A SEO or an SEO

The rule is simple but rarely taught: choose the article based on how the acronym sounds when spoken, not the first letter you see. SEO is an initialism: each letter is said individually – S-E-O. The letter S begins with a vowel sound ("ess"), so you write an SEO. That covers almost every situation in SEO writing: job titles ("I am an SEO"), descriptions ("an SEO strategy"), and questions ("an SEO audit").

What trips people up is seeing the consonant S and reaching for 'a' by reflex. That instinct works for words like 'a site' because 'site' is a word pronounced with a consonant sound. But for acronyms and initialisms, the ear decides. Try saying the two options aloud: "a SEO" forces you to insert a glottal stop or slur the vowel; "an SEO" flows naturally.

There is one edge case. If you treat SEO as an acronym that you pronounce as a single syllable – "see-oh" – then 'a SEO' becomes phonetically consistent because you're starting with a consonant sound. You hear that sometimes in casual conversation, especially from people who work in the field and want to say it fast. But in writing, especially professional or formal writing, stick with 'an SEO'. The industry standard, from Google's own documentation to the most popular guides on [SEO](/seo/), uses 'an'. It signals that you know the convention.

This decision seems trivial until you are the one editing a page or writing a proposal. In practice, the article choice matters in three specific places:

Job postings and resumes. A role that says 'We are hiring a SEO specialist' suggests a lack of polish or a rushed job description. The same candidate who writes 'I am a SEO' on their CV looks less meticulous than one who writes 'an SEO'. Given that [SEO consulting](/seo-consulting/) and [SEO strategy](/seo-strategy/) roles are competitive, small signals like this accumulate. I have seen hiring managers notice it.

Client-facing content. If you publish blog posts, guides, or case studies that mix 'a SEO' and 'an SEO', readers – especially non-SEO professionals – may question your attention to detail. They might not articulate it, but the inconsistency erodes trust. Clients pay for precision; inconsistent grammar implies inconsistent work.

Documenting processes internally. When you write [SEO best practices](/seo-best-practices/) for your team or a client, the language should be unambiguous. Using 'a SEO' can momentarily confuse someone who reads it as a word rather than an initialism. Keeping to 'an SEO' removes that friction.

Does it ever not matter? In informal chat, group messages, or internal Slack threads, no one cares. Write 'a SEO' there and nobody will correct you. But the moment that text becomes public or even semi-public – a shared drive document, a client presentation – the standard changes. I treat it like any other style rule: pick the version that never gets flagged, and that is 'an SEO'.

For the first few years I worked in SEO, I wrote 'a SEO' without thinking. The logic seemed airtight: S is a consonant, so it wants 'a'. I had internalised the primary-school rule about articles and consonants versus vowels, and I applied it blindly. It took a client editing a proposal and changing every 'a SEO' to 'an SEO' for me to question my own rule. I checked Google's SEO Starter Guide and Moz's What Is SEO? – both consistently use 'an SEO'. That forced me to learn the difference between words and initialisms.

What I still get uncertain about is the conversational edge case. When I am speaking quickly at a conference or on a call, I sometimes say 'a SEO' because I pronounce it as "see-oh". Should written transcripts of that speech preserve the spoken form? I think yes, for authenticity, but then you get the mismatch between the transcript and the polished blog version of the same talk. I have not settled on a clean answer for that.

Another thing I got wrong: I assumed the rule only applied to the person ("an SEO"), not to the discipline. I would write 'a search engine optimisation strategy' but 'an SEO strategy'. That is correct, but I was using the wrong reason. I now treat all references to the acronym the same way. The only exception is when I write out the full phrase – then 'a' is right: 'a search engine optimisation' because the first sound is consonant. That consistency makes the decision automatic now, and it saves me from the edit later.