Build an SEO Content Brief from Browser Research
An SEO content brief should help a writer produce the best answer for a real reader. It is more than a keyword list: it defines the problem, evidence, boundaries, structure and contribution that make the page worth publishing.

Write the reader and outcome
Describe who is searching, what situation they are in and what they should be able to do after reading. A brief for a beginner fixing crowded Chrome tabs differs from a developer designing a browser extension, even when both mention tabs.
State the primary intent in one sentence and list adjacent questions separately. This stops the article from becoming a collection of every related phrase.
Review the existing result landscape
Open a small sample of strong results and identify what each page actually provides: instructions, comparison, definition, tool or first-hand test. Note repeated gaps, outdated claims and areas where your product experience or research can add something useful.
Do not copy headings or rewrite competitors. Use the review to understand reader expectations, then design a clearer structure and original contribution.
Attach evidence to planned claims
List the material claims the article expects to make and attach a primary or authoritative source to each. Include dates and product versions for information that can change. Label inference, opinion and first-hand observation separately.
If evidence is missing, convert the claim into a research question or remove it. A polished brief should not pressure a writer to state uncertain information confidently.

Plan structure and internal links
Outline sections in the order a reader needs them: direct answer, necessary context, steps, edge cases and verification. Choose related pages that genuinely deepen the task, and write descriptive anchor text explaining what the reader will find.
Every important page should be linked from another relevant page. Also identify where the new article should link back to a broader guide so the site forms a navigable topic cluster.
Idea: add a differentiation field
Include a required brief field called 'Why this page deserves to exist'. The answer might be an original workflow, tested implementation, clearer comparison, unique data or better evidence. If the answer is only 'target the keyword', revise the plan.
Add an explicit exclusion list for claims, audiences or tangents that belong elsewhere. Boundaries protect depth and reduce overlap with existing articles.
Define review and measurement
Before publishing, check factual support, title and description accuracy, heading structure, links, image context, canonical URL and schema. After publication, confirm crawlability and sitemap discovery, then monitor relevant queries and page impressions.
Use early performance data carefully. Improve the page when evidence shows a mismatch or missing answer, and preserve a dated note explaining why the change was made.
Tabzero: Browser Tab Manager & Notes
Save tab links, keep notes beside your sources, and return to what matters. Tabzero is in development preview; AI Notes remains planned.
Related guides
Organize Competitor SEO Research with Browser Tab Groups
Compare competitor pages, search intent, evidence, internal links, and content gaps with a fair browser-tab research structure.
A Browser Tab Workflow for a Technical SEO Audit
Organize crawlability, indexation, canonical, sitemap, structured data, performance, and validation evidence without losing audit context.
Turn Search Console Queries into Useful Content Ideas
Use Search Console pages, queries, impressions, clicks, CTR, and position to prioritize content updates and distinct new articles.