Take two articles on the same topic: one ranks and the other doesn't, and the difference is usually not the number of keywords. The text that ranks gives users the information they were looking for with that query, without making them open another tab. The other one talks about the topic but doesn't answer the question that was asked. Writing SEO-friendly content means building a production process that doesn't leave this difference to chance.
Google's own documentation directly answers the most frequently asked part of the process: the search engine has no preferred word count, and if you're writing to reach a number you've heard, that's a warning sign that you should reassess the content. The same logic applies to density ratios, mandatory paragraph lengths and heading character limits. The criterion is not the form of the text but whether the question has been fully answered.
SEO-friendliness is a property of the match, not of the text
You can't recognize SEO-friendly content by examining the text on its own. SEO-friendliness is a matter of matching: it emerges when a specific query, the information need behind that query and the answer the page provides overlap. That's why the same text can be a perfect fit for one query and completely irrelevant for a neighboring one.
In practice, this means that if you haven't decided which question the page will answer before you start writing, no amount of later editing will make the text a good fit. Google's content guidance looks at it from the same angle: readability and clear organization, writing from your own knowledge rather than copying others, staying up to date and genuinely helping the reader all sit side by side on the same list. These are not formal rules; they are criteria for the quality of the answer.
The sequence below lays out the steps for building that match. The order matters, because each step uses the output of the previous one as its input.
- Decoding the intent behind the query
- Choosing the questions to answer on a single page
- Building the structure around those questions
- Writing the answer directly and with evidence
- Writing the title and description
- Reading the page's real query footprint after publishing
Reading the intent behind the query
The most reliable indicator of what kind of page answers a query is the search results themselves. Search for the query and look at the types of results on the first page, and you'll see which intent dominates: if guides appear, the user wants to learn; if category and product pages appear, they're at the buying stage; if comparison content appears, they're trying to make a choice. This reading is more concrete than the intent labels in tools, because it shows directly which answer format Google considers appropriate for that query.
Cases where the same keyword phrase carries more than one intent are the most common source of mistakes. A phrase like "content writing" is searched by someone curious about the profession, someone looking for a job and a business looking to buy the service alike. These three intents can't be met by a single page; when you try, you end up with a text that fully answers none of them. The details of matching queries to page types are covered in our piece on search intent and user alignment.
Deciding which questions a single page will answer
Once the intent is clear, the next job is to narrow the scope. Covering every angle of a topic in a single article is often impossible, and when you force it, the page turns into a collection of loosely related sections. The right question is: what is the smallest set of questions that will leave a reader arriving with this query satisfied when they close the page?
The practical way to build this set is to collect the follow-up questions around the main query. The related question boxes in search results, autocomplete suggestions and the subheadings of the top-ranking results give you this list quickly. Once you have the list, the second decision follows: which questions stay on this page, and which deserve a page of their own?
If you skip this distinction, multiple pages answering the same question pile up on the same site, and those pages start replacing one another for the same query. The problem isn't that the pages are bad; it's that nobody can tell which one owns the query. You can measure whether such a conflict exists among your current pages using the method we describe in our keyword cannibalization check.
Building the structure around the questions
The outline is simply the questions chosen in the previous step, put in order. Each main question becomes a section heading, and the only job of the text under that heading is to answer that question in full. Section headings should say clearly what the content covers, without being fancy or vague. A reader should be able to tell whether the page answers their question just by scanning the headings.
A consistent heading hierarchy is the technical counterpart of that scannability. The page has a single main heading, the sections sit one level below it, and the subdivisions of the sections sit one level below those. Skipping levels breaks the structure both for visitors using screen readers and for systems that evaluate the page by splitting it into sections. Google's starter guide keeps this point simple: break long text into paragraphs and sections, and use headings to make navigation easier.
A common trap when building the structure is applying a ready-made section template to every article. Sections that follow the same order regardless of the topic leave the reader's actual question buried in the middle of the page. The section order is determined by the logic of the question, not by a template: in topics that require a decision, the criteria come first; in topics that require implementation, the sequence of steps comes first.
Writing the answer directly and with evidence
If a section answers a question, the answer itself should sit at the start of the section. Warm-up sentences, introductions about the importance of the topic and lead-ins preparing the reader for what the section will cover all delay the information being sought. The answer comes first, the explanation next, examples and exceptions last.
The second thing that determines the strength of an answer is what its claims are based on. Using verifiable information instead of generic statements keeps readers from leaving the page to search for the same question elsewhere. One of Google's self-assessment questions asks exactly this: does the content leave readers needing to search again to get better information? Naming a source, giving a number with its context, or sharing the kind of detail that comes from actually having applied a method closes this gap.
The third is original value. Restating in different words what ten pages on the same topic already say adds nothing to the information already in the search results. Google's quality questions probe this from two angles: does the content provide original information, reporting, research or analysis, and if it draws on other sources, does it add substantial value rather than simply copying or rewriting them? A text that fails both questions will struggle to rank, even if its form is flawless.
The fourth is language. Whether readers understand a sentence on the first read matters more than any formal rule. Needlessly long sentences, heavy words chosen when simpler ones would do and technical terms left unexplained don't make a text look expert; they only slow it down.
Where AI-written content fits in this process
Google's stance on the subject looks at the outcome, not the production method: what is evaluated is how helpful the content is to the reader, not how it was produced. But the same documentation also draws the line clearly. Using automation or AI to generate content with the purpose of manipulating rankings is a violation of the spam policies, and that policy classifies producing many pages without adding value for users as scaled content abuse. Using generative AI tools to create many pages without adding value is explicitly listed as an example.
The practical distinction is this: model output is a draft, not a text ready for publication. Unverified numbers, nonexistent sources and mistakes that someone who has actually done the work would spot all make their way onto the page like this. Google also recommends disclosing how content was produced in cases where readers might wonder: is the use of automation visible to visitors, and is it explained why it was used?
Getting the same text cited as a source in AI answers is a separate matter and requires different decisions from classic search optimization. We cover that side separately in our article on how to write content that gets cited by AI.
Writing the title and description
The title tag is the page's name in the search result and the place where the click decision is made. Google's title documentation asks for three things: every page should have its own title, the title should be descriptive and concise, and the same words shouldn't be repeated over and over. Vague phrases and titles that line up variations of the same keyword are weak for the same reason: neither tells the user what the page is.
The answer to the character limit question is in the same document. There is no limit on the length of the title tag; the part shown in search results is truncated when necessary, and that truncation is typically based on device width. So the goal isn't to hit a specific number, but to make clear what the page is within the first few words.
The description doesn't determine rankings, but it is one of the sources of the snippet shown in the result. Google mostly generates the snippet from the page's own content and sometimes uses the description tag. A good description is short, unique to that page and includes the page's most important points. The practical conclusion: the page's promise should be clear not only in the description tag but also in the first paragraph of the text.
Titles that overpromise to spark curiosity can bring clicks in the short term. One of Google's quality questions targets this directly: does the main heading avoid being exaggerated or shocking in nature? The wider the gap between the title and what the page delivers, the more readers bounce back, and the click you gained doesn't turn into a lasting gain. The click-through side of title writing is covered in detail in our article on CTR-focused title optimization.
Pre-publication self-assessment checklist
Google's own documentation lists the questions to ask about content before you publish it. The list below was compiled from those questions so you can quickly test whether an article is ready to publish. All the answers are expected to be yes.
- Would your existing audience, who come to your site directly, find this content useful?
- Does the text carry first-hand knowledge that comes from actually having worked on the topic?
- Will readers feel they've learned enough to achieve their goal once they finish the article?
- Does the content provide original information, reporting, research or analysis?
- Does it cover the topic comprehensively instead of staying on the surface?
- If it draws on other sources, does it add value instead of copying them?
- Does the main heading summarize the page's content accurately and descriptively?
- Does the main heading tell the truth without resorting to exaggeration or shock?
- Is the text free of spelling and style errors, and does it look carefully produced?
- Is it clear to the reader where the information comes from, who the author is and why they know the topic?
- Is it free of factual errors that could easily be verified?
- Does the reader leave this page without having to search for the same question in another source?
The questions on the list are decision tools, not measurements. When you run an article through these questions, the gap usually comes down to a single item: either the scope is too narrow, the claims are unsupported, or the text repeats what others have said.
Habits that pass for SEO-friendly but cause harm
The four habits below still circulate as advice. None of them has any basis in Google's documentation, and for some of them, the documentation says the exact opposite.
Calculating a keyword density ratio
Spreading a keyword through the text to reach a specific percentage has no documented basis. Google's spam policies define the opposite: filling a page with keywords in an attempt to manipulate rankings counts as keyword stuffing, and repeating the same word or phrase so often that it sounds unnatural is explicitly listed among the examples of this definition. A writer working from a ratio is unknowingly writing toward that line.
Piling synonyms and related terms into the text
The modern version of the density idea is cramming terms with the same meaning into sentences. The result is the same: sentences lose their natural flow, the reader struggles, and the text starts to read like a keyword list. Related terms naturally enter a text that genuinely explains the topic; they don't need to be sprinkled in afterward.
Updating the date without changing the content
Moving a page's date forward just to make it look fresh is one of the behaviors on Google's warning list for search engine-first content. The warning asks directly: are you changing the date of pages to make them seem fresh when the content has not substantially changed? What should trigger an update is not the calendar but information actually going out of date. When information that changes, such as prices, versions, regulations and tool names is refreshed, the date becomes meaningful on its own.
Replicating the same template across many pages
Spreading a single template across dozens of pages by swapping words sits right at the center of the definition of scaled content abuse. Google defines this as producing many pages with the purpose of manipulating rankings rather than helping users, and recommends that sites hosting such content remove it from search. A small number of pages that genuinely answer their question in full perform better, for both readers and systems, than many superficial pages.
Reading the page's real query footprint after publishing
The queries a page appears for are rarely identical to the list you anticipated while writing. Search Console's performance report shows this difference: when you apply a page filter, the queries that URL received impressions for, along with their average positions and click counts, become visible. The real insight here isn't the top keyword, but the queries that get impressions without getting clicks.
There are two typical situations. If the page gets impressions for an unexpected query, that question is either missing from the text or only mentioned in passing; adding or deepening the relevant section is often the quickest win. If the page gets impressions for the target query but no clicks, the problem isn't the content but the title and snippet shown in the search result.
The decision to update also comes from this report. Google's starter guide lists reviewing published content, updating it when necessary and removing it if it's no longer relevant in the same sentence. This doesn't mean every page should be overhauled periodically; the data tells you which page needs maintenance. We've collected the method for reading the report regularly in our article on tracking Search Console data.
Frequently Asked Questions
How many words should SEO-friendly content be?
Google has no preferred word count, and its documentation says so explicitly. Writing to reach a particular length is on the warning list for search engine-first content. The right length is the point at which the chosen questions have been fully answered and the next paragraph would only produce repetition. In a definition article that point comes early; in a multi-step implementation guide it comes late.
Do I have to include the keyword in the title?
It's not mandatory, but in most cases it's the natural result. The title has to describe what the page covers, and the words readers use to search for a topic usually overlap with what the page covers. It becomes forced when you bend the sentence to squeeze the keyword in. Google's title guidance warns against exactly this: repeating the same words and phrases in a title over and over doesn't help users.
Should I write a second article on the same topic or expand the existing one?
It comes down to intent. If the new query carries a different information need, it deserves its own page; if it's just the same need expressed in different words, expanding the existing page is the right decision. In the second case, opening a separate page causes the two pages to replace each other for the same query and weakens both.
When should you evaluate the results of published content?
There's no fixed period, and giving a number of days would be misleading. Evaluation is driven by data, not the calendar: once the page starts getting impressions in Search Console, there's something to measure; until it does, the task is to check whether the page has been indexed. The level of competition, the site's existing visibility and the query volume prevent this timeframe from being reduced to a single number.
Does having AI write the content lower rankings?
The production method on its own is not a reason for a penalty; what is evaluated is the value the resulting content provides to the reader. The risk arises when automation is used to produce many low-value pages with the purpose of manipulating rankings. The difference lies in whether the output has been verified and whether the page actually says something new.
