SEO writing and feedback
What rejection taught me about better SEO writing
Rejection hurts, but it can reveal what the next draft needs. Answer sooner, match intent, make the page easy to scan, show proof, and revise toward the reader’s decision.
Separate a rejection from a reason to revise
This article began in 2012 as a personal reflection on rejected SEO-writing pitches and painful feedback. The practical question remains: what does the next draft need to do better for its reader?
A rejection by itself does not identify a writing fault. The brief, budget, timing, sample choice, or fit may have affected the decision. Use specific feedback when it is available, and check it against the work before changing the draft.
For a page meant to answer a search question, start with that question. Can the reader find the answer, understand its limits, and take the next useful step?
Turn a vague comment into an editing check
“The opening is slow”
Identify the sentence that first answers the reader’s question. Move it earlier if the preceding context is not needed to understand it. Keep essential qualifications beside the answer.
“This misses the brief”
Compare the title, intended audience, promised answer, and body. A guide to choosing a service is a different task from a general explanation of how the service works.
“It sounds generic”
Find a claim that could describe almost any business. Replace it with a relevant example, a choice the reader must make, or evidence for the claim. Ask for missing facts rather than inventing them.
“I do not know what to do next”
Check the ending and relevant links. Name the next question, document, comparison, or action. A link should help the reader continue the task, not merely add another page view.
Rewrite one opening around a real question
Suppose the assignment is a page explaining what to send for a furniture-reupholstery estimate. This is an editing exercise, not a quotation from the rejected pitches.
Weak opening: “Furniture plays an important role in every home, and upholstery is an excellent way to give beloved pieces a new lease of life.”
More useful opening: “For a reupholstery estimate, send photos of the whole chair, the damaged areas, and the underside, plus its approximate dimensions. Tell the upholsterer whether you want the padding repaired as well as the fabric replaced.”
The revision answers the task immediately. Before using it on an actual business page, confirm that these are the details that business needs. Add its accepted contact route and explain what still requires an inspection.
The supporting headings can now follow the same decision: photos to send, measurements to include, repairs to describe, and what the estimate covers. The introduction no longer has to carry the whole explanation.
Keep the detail that makes the answer usable
Direct writing can still be thorough. A short answer may need evidence, exceptions, examples, and instructions. Remove repetition before removing information the reader needs.
Academic and search writing both vary in form. For a practical search question, make the answer easy to locate; do not assume that every essay is slow or that every search visitor wants a short page.
- Examples: show the decision or action, and label invented scenarios clearly.
- Evidence: link the source of a factual claim and explain relevant limits.
- Structure: use headings and lists where they help a reader find or follow information.
- Length: stop when the question is answered. Google’s helpful-content guidance explicitly rejects the idea of a preferred word count.
Revise the page in a useful order
- State the reader’s job: Write one sentence describing what they need to learn, compare, fix, buy, or verify.
- Check the promise: Make sure the title and opening match that job and the body delivers it.
- Read only the headings: They should show where the important answers are. Replace labels that reveal nothing about the section.
- Check the proof: Mark unsupported claims, missing sources, and examples that do not explain anything. Resolve them before polishing the prose.
- Remove repetition: Keep necessary context and qualifications; cut repeated introductions and conclusions.
- Test the next step: Open the relevant link or contact route and confirm that it continues the task.
For a rejected sample, keep the brief and feedback beside both versions. That makes it possible to explain what changed and why, rather than simply saying the new version reads better.
Check understanding before claiming success
Ask a reader to use it
Give someone the task and the revised page. Ask them to find the answer and describe the next step. Watch where they hesitate without explaining the page for them.
Interpret behavior carefully
Relevant internal-link clicks, clearer enquiries, and fewer unanswered basic questions can help you assess usefulness. Time on page alone is ambiguous: a quick visit may mean the reader found the answer, while a long one may mean confusion.
Keep search results in context
Review whether the page appears for the question it answers. A ranking change or enquiry after an edit does not by itself prove that the wording caused it. Use search evidence alongside the reader test.
Choose one revision to practise
Take a draft and mark its first useful answer. Improve the route to that answer, then ask another reader to complete the same task. The feedback now concerns something you can observe and change.