This is a conceptual sequence, not a directly divisible analytics report: URLs, impressions, clicks, and conversion events use different units. No traffic or conversion data is invented.
SEO guarantees neither indexing nor rankings. Technical rules here refer to Google documentation; verify other engines separately.
Search intent
The task someone wants to complete with a search.
Hypothetical example: Suppose someone searches “compress images without losing quality”: they may want a tool now.
Do not confuse: Your sales goal is not necessarily their goal; intent is a hypothesis.
Evidence to look for: Result-page formats, users’ own words, and usability feedback.
Keyword / query
A query is what someone searches; a keyword is a term you use to plan content.
Hypothetical example: Suppose the query is “make png smaller”; you group it under PNG compression.
Do not confuse: Synonyms need not each get a page; repetition is not the goal.
Evidence to look for: Search Console queries, interview language, and related search results.
Long-tail keyword
A less frequently searched query, often expressing a more specific need.
Hypothetical example: “Batch compress transparent PNGs” is more specific than “images”; volume still needs evidence.
Do not confuse: Long-tail does not just mean more words, or guarantee easy rankings or conversions.
Evidence to look for: Query detail and demand evidence; tool volumes are estimates.
SERP
The full results page, which can include organic results, ads, and other features.
Hypothetical example: For “image compression”, note whether leading results are tools, guides, or comparisons.
Do not confuse: An ad is not an organic ranking; one screenshot is not everyone’s result.
Evidence to look for: Record query, time, region, device, and result formats.
URL discovery
The search engine learns that a URL exists.
Hypothetical example: An existing guide links to a new tool, providing a discovery path.
Do not confuse: Discovery does not mean the URL was crawled or indexed.
Evidence to look for: URL Inspection status and available referring-page or sitemap information.
Crawling
A crawler requests a page and its resources from the server.
Hypothetical example: Suppose Googlebot requests /compress and the server returns a page.
Do not confuse: A successful response does not prove indexing.
Evidence to look for: Last crawl and fetch status in URL Inspection; verified server logs when needed.
Rendering
Running page code to assemble the readable page.
Hypothetical example: If JavaScript loads instructions, check that rendered content contains them.
Do not confuse: Working in your browser does not prove equivalent crawler access.
Evidence to look for: Rendered HTML, screenshots, and resource-loading results in URL Inspection.
Indexing
The engine processes a page and stores information in its search index.
Hypothetical example: Suppose URL Inspection reports the page indexed: it has entered the searchable index.
Do not confuse: Being indexed does not guarantee appearance for a particular query.
Evidence to look for: URL Inspection and Page indexing reports, not just site: result counts.
Ranking
How the engine selects and orders results for a query.
Hypothetical example: A tool may rank differently for “PNG compression” and “shrink JPG”.
Do not confuse: There is no permanent site-wide rank across all queries and regions.
Evidence to look for: Inspect Search Console by query, page, country, and device.
Impressions
Your link received a recorded search-result impression under that result type’s rules.
Hypothetical example: Suppose the report shows 100 impressions: it records 100 qualifying appearances.
Do not confuse: Impressions are neither unique people nor clicks.
Evidence to look for: Search Console impressions with consistent search type, dates, and filters.
Clicks
Recorded clicks from search results to your site.
Hypothetical example: Suppose Search Console records 10 clicks; next check whether visitors completed their task.
Do not confuse: Clicks are not sessions, unique people, or purchases.
Evidence to look for: Read Search Console clicks and site analytics separately; their definitions differ.
CTR
Clicks divided by impressions within the same reporting scope.
Hypothetical example: Hypothetical: 5 clicks / 100 impressions = 5% CTR.
Do not confuse: No single good CTR applies to all positions, queries, and result formats.
Evidence to look for: Compare like queries and devices; zero impressions give no meaningful CTR.
Average position
GSC’s mean recorded position across impressions; property aggregation uses the topmost result.
Hypothetical example: Simplified example: positions 2 and 8 across two impressions average to 5.
Do not confuse: An average of 5 does not mean everyone saw you fifth.
Evidence to look for: Hold query, page, country, and device steady; read alongside impressions and clicks.
Usage / conversion
A visitor completes a valuable action you defined in advance.
Hypothetical example: Suppose the tool’s goal is a successful compressed-file export; track that success event.
Do not confuse: A page visit is not automatically a conversion; a GA4 key event is not automatically revenue.
Evidence to look for: Validate event firing, then inspect real usage, leads, or orders.
robots.txt
A root-level file giving compliant crawlers rules about which paths they may crawl.
Hypothetical example: If crawling /drafts/ is disallowed, external links can still reveal those URLs.
Do not confuse: robots.txt is not a reliable deindexing or privacy mechanism.
Evidence to look for: Inspect the live /robots.txt and crawl-allowed status in URL Inspection.
noindex
A directive asking supporting engines to exclude the page from search results.
Hypothetical example: Suppose a public test page has noindex; check it was removed from the intended live page.
Do not confuse: Google must crawl the page to read noindex; it is not access control.
Evidence to look for: Inspect robots meta, X-Robots-Tag, and crawl access.
Canonical URL
The representative URL you recommend for duplicate or very similar content.
Hypothetical example: If /compress?ref=news duplicates /compress, recommend the clean URL.
Do not confuse: Canonical is a signal, not a command, redirect, or deletion.
Evidence to look for: Compare declared and Google-selected canonical URLs.
Sitemap
A file listing important URLs you want search engines to discover.
Hypothetical example: Suppose you add a tool: include its preferred URL and check sitemap processing.
Do not confuse: Successful submission guarantees neither crawling nor indexing and does not replace navigation.
Evidence to look for: Check accessibility, processing status, and correctness of listed URLs.
Internal link
A link from one page of your site to another.
Hypothetical example: A PNG guide links to its tool using “batch compress PNGs”.
Do not confuse: A sitemap entry is not an internal link; important links should be usable and crawlable.
Evidence to look for: Check anchor hrefs, destination responses, and descriptive link text.
Backlink
A link from another website to yours; your link to another site is outbound.
Hypothetical example: Suppose a design tutorial independently references your compression tool.
Do not confuse: Link count is not quality; buying or selling links to manipulate rankings is risky.
Evidence to look for: Inspect the source page, context, relevance, and referral visits.
hreflang
An annotation identifying equivalent language or regional versions for Google.
Hypothetical example: Suppose /zh/compress and /en/compress list both themselves and each other as zh/en alternatives.
Do not confuse: It does not translate pages or make unrelated pages equivalents.
Evidence to look for: Check reciprocal/self references, full URLs, language codes, and equivalent content.
Page title / title link
Your title describes the page; Google may generate the result’s title from multiple sources.
Hypothetical example: Suppose the title promises a transparent-PNG batch compressor, and the page supports it.
Do not confuse: HTML title, visible H1, and search-result title are distinct.
Evidence to look for: Compare title, visible heading, actual results, and page capabilities.
Meta description / snippet
You can provide a description; Google may instead build the snippet from page content.
Hypothetical example: Suppose the description says “preserves transparency and supports batches”; verify both.
Do not confuse: Providing a description does not guarantee it appears verbatim.
Evidence to look for: Compare the description, page text, and snippets for different queries.
Search intent, keyword grouping, and long-tail are working definitions for this guide. Linked Google guidance supplies background, not an official Google taxonomy or metric.