Useful search research begins with a specific question: what answer does the reader need, on which engine and in which market? This library connects editorial decisions with technical checks. The methods and downloadable worksheets require no registration.
Choose your starting point
For a new page, start with the keyword selection guide. For an existing page with little visibility, start with the indexing diagnostic. For a year-end offer, use the Q4 workflow and contribution calculator. Each resource addresses a different task.
A method with four decisions
1. Describe the task and context
Record the problem, country, language, engine and page that might answer it. “Diagnose an unindexed product page” supports concrete checks. “Do SEO in the US” is too broad to choose evidence or a destination. For Canada, distinguish French and English questions where readers and results differ.
2. Preserve the origin of each observation
A customer question, a tool’s estimated volume and a Search Console query provide different information. Record their source and date in separate columns. Leave unavailable metrics blank. The worksheet’s three rows are fictional scenarios to replace; they do not claim to measure demand.
3. Choose an answer and its evidence
Group variations that require the same procedure. A comparison needs criteria, a tutorial needs executable steps and an outcome claim needs measurements. Before creating a page, check whether an existing answer can be improved. A local edition is justified when context changes the work, conditions or sources.
4. Measure the stages separately
First check that the page is accessible and its discovery links work. Then examine its state in available consoles, followed by impressions and clicks. Keep visits to your offer and orders in a separate record. When comparing periods, use the same market and metric definition.
Which checks apply to each engine?
For a publication serving the United States, United Kingdom and Canada, start with engines your readers use and that you can measure. The links below lead to operators’ documentation. Engines may share a source without displaying identical rankings. A submission or notification does not prove that a page is indexed.
- Google — official documentation
Search Console: inspect a URL and its performance; retain the exact wording of observed states.
- Bing — official documentation
Webmaster Tools: verify ownership, examine pages and notify relevant changes through IndexNow.
- Brave — official documentation
Read the crawler guidance and check HTML access. Its index deserves a separate check.
- DuckDuckGo — official documentation
Its sources include Bing and other services. Checking a DuckDuckGo result remains a separate observation.
- Yahoo — official documentation
Support directs website inclusion to Bing. Then observe the result actually displayed on Yahoo.
- Ecosia — official documentation
Check the provider applicable to the context: partners and results can vary.
- Qwant — official documentation
Check QwantBot access and discovery links; inclusion and ranking are different observations.
- Yandex — official documentation
Use Webmaster where this engine serves your audience, verifying the exact domain and ownership rights.
Separate crawling, indexing and traffic
An HTTP 200 response shows that a request received content; it does not establish inclusion in a search engine. A fetched sitemap and a URL known to the index are different states, too. The sitemap diagnostic protocol gives an order of checks and a record for retaining evidence.
When a crawler encounters a block, begin with logs: URL, time, status and observed IP. Our AI crawler IP verification procedure and open source script compare an address with operators’ published prefixes. A prefix match has a limited scope; the guide explains complementary checks.
Advertising, APIs and organic search
A keyword may support an article, a product category or an advertising campaign. Establish the objective before comparing figures. An advertising competition indicator and an estimated SEO difficulty describe different activities. Each tool’s documentation should explain the field being used.
For APIs, first identify the system and data exchanged: a product offer, a web page or a change event. An integration requires its own access rights and checks. A successful technical call needs to be followed by an observable user outcome.
Build a useful research record in one session
- Choose one customer question and one market.
- Record the existing answer and what it lacks.
- Save a primary source and a dated observation.
- Choose whether to update, create a distinct answer or investigate further.
- Add the useful next action and the check to perform after publication.
Visit the free tools and code library for worksheets, structured-data testing and performance tools. For a commercial campaign, the Q4 dossier connects page preparation, offer conditions and measurement. These destinations help continue a specific task.
Resources checked on October 3, 2026. Editorial team: Search Engine Trends.
About historical links to the forum
This domain previously hosted a search-engine discussion forum. Its historical discussions are not available here. This page provides new editorial resources and does not recreate those messages.