Technical and On-Page SEO Glossary

Technical and On-Page SEO Glossary for B2B Marketers

In B2B marketing, this glossary defines 22 audit, infrastructure, on-page, and measurement terms tied to organic pipeline performance under constrained budgets and long sales cycles. Every entry is written for marketers who need to defend SEO investment to a CFO, prioritize a fix backlog without engineering headcount, and connect ranking signals to a six-month sales cycle. This is not an SEO dictionary. It is an audit-to-pipeline vocabulary map for B2B.

Most glossary sources (Semrush, Yoast, Wordstream) define SEO terms for e-commerce or SMB contexts, leaving B2B marketers translating consumer-shaped definitions into enterprise-shaped problems. Google Search Central documentation (2024) notes that indexation eligibility, not raw page count, governs whether content can earn search traffic. The Starr Conspiracy built this glossary to map terminology to a workflow: diagnose, prioritize, fix, measure. Use it to defend budget, triage a backlog of pipeline-eligible URLs, and align SEO work with sales-cycle timing.

How These Terms Relate

The four categories below are mutually exclusive and mirror the workflow a B2B SEO audit actually follows. Audit Foundations name the diagnostic concepts. Technical Infrastructure names the systems Googlebot interacts with. On-Page Elements name the signals you control inside a URL. Measurement and Prioritization name the outputs that translate fixes into pipeline conversations. Indexation is eligibility, ranking is selection, traffic is attendance, pipeline is the scoreboard. Every week your indexation is broken, your pipeline clock resets. A term like crawl budget only matters once you connect it to indexation, which only matters once you connect it to organic sessions on revenue pages.

Audit Foundations

Technical SEO

In B2B, technical SEO is the practice of optimizing a site's infrastructure, crawlability, rendering, and indexation so search engines can access and understand published content.

How it works. Technical SEO covers server response, HTML delivery, JavaScript rendering, sitemap and robots configuration, canonicalization, and structured data. Google Search Central documentation (2024) is explicit: if Googlebot cannot fetch and render a page, the page cannot be indexed and cannot rank, regardless of content quality. For B2B teams with no engineering headcount, technical SEO is the unglamorous work that determines whether published content is even eligible to compete.

Examples. Diagnosing JavaScript rendering issues in a Next.js marketing site using Google Search Console's URL Inspection tool; auditing canonical configuration after a CMS migration; using Lighthouse to flag render-blocking resources.

Related terms:

• Crawl budget
• Indexation
• Rendering
• Core Web Vitals

FAQs.

• Is technical SEO worth the engineering time? If indexation is broken, every other investment compounds at zero. Fix indexation first.
• Can marketers do technical SEO without developers? Diagnosis, yes. Implementation usually requires engineering for anything beyond CMS-level controls.
• How often should we audit? Quarterly at minimum, plus after any deploy that changes URL structure, templates, or rendering.

Bottom line. Technical SEO determines pipeline eligibility. If engineering is not on your side, your backlog is fiction.

On-Page SEO

In B2B, on-page SEO is the optimization of elements inside a single URL, including title tags, headings, body content, internal links, and schema, to win the query and keep the buyer reading.

How it works. On-page SEO aligns a URL's signals with the intent behind a query and with the expertise signals Google uses to assess quality. Google evaluates content quality and helpfulness alongside structural signals (Search Central, 2024). For B2B, on-page is where you prove expertise to a skeptical buyer reading an 1,800-word comparison page.

Examples. Rewriting a title tag to lead with the buyer's problem, not the product name; adding a comparison table to a category page; embedding cited primary research with named authors.

Related terms:

• Title tag
• Meta description
• E-E-A-T
• Internal linking

FAQs.

• Is on-page still worth doing if rankings have stalled? Yes. On-page changes affect click-through and dwell, which influence ranking durability.
• What's the highest-leverage on-page fix? Title tag and H1 alignment to the query, then internal links from hub pages.
• Does on-page replace technical SEO? No. On-page assumes the page is indexable.

Bottom line. On-page SEO converts indexed URLs into clicked URLs into read URLs.

SEO Audit

In B2B, an SEO audit is a structured diagnostic of a website's technical, on-page, and off-page health that produces a prioritized backlog of fixes ranked by pipeline impact, effort, and risk.

How it works. A B2B audit scopes the crawl to pipeline-eligible URLs (homepage, category, comparison, solution, pricing, top-converting blogs), then evaluates indexation, rendering, on-page signals, internal link distribution, and Core Web Vitals against benchmarks. The Starr Conspiracy uses an impact-effort-risk rubric to produce CFO-proof prioritization.

Implementation notes. Scope an audit to the 200 URLs that touch pipeline rather than crawling 40,000. Use Screaming Frog plus Google Search Console's Pages report to reconcile crawl status with index status. Produce a fix backlog ranked by revenue exposure. A sample backlog item might read: "Fix canonical chain on /pricing, Impact: 9 (pipeline URL), Effort: 2 (CMS-level), Risk: 1, Priority: P0."

Related terms:

• Crawl budget
• Indexation
• Core Web Vitals
• Organic traffic

FAQs.

• How long should a B2B SEO audit take? Two to four weeks for a focused, pipeline-scoped audit.
• Full-site crawl or scoped crawl? Scoped. Most B2B sites have too much low-value URL volume for a full crawl to surface signal.
• What is the deliverable? A prioritized backlog tied to pipeline-eligible URLs, not a 200-page PDF.

Bottom line. An audit that does not end in a CFO-proof backlog is a research project, not a fix plan.

E-E-A-T

In B2B, E-E-A-T is Google's quality framework standing for Experience, Expertise, Authoritativeness, and Trustworthiness, used by human raters and reflected in ranking systems.

How it works. E-E-A-T signals include named authors with verifiable credentials, cited primary research, original data, and clear publisher identity (Search Central, 2024). For B2B, generic agency bylines and recycled secondary sources fail this test against buyers who already know the space.

Examples. Replacing "Marketing Team" bylines with named practitioner authors and LinkedIn-linked bios; citing original survey data with sample size and date; adding reviewer credentials to expertise.

Related terms:

• Topical authority
• Search intent
• On-page SEO
• Schema markup

FAQs.

• Is E-E-A-T a direct ranking factor? It is a framework reflected across multiple signals, not a single score.
• How do we prove experience for B2B topics? Named practitioners with verifiable work history beat anonymous content every time.
• Does E-E-A-T matter outside YMYL? Yes. B2B buyers apply the same scrutiny as raters do.

Bottom line. E-E-A-T is how Google and your buyer ask the same question: who are you to say this?

Search Intent

In B2B, search intent is the underlying goal behind a query, typically classified as informational, navigational, commercial, or transactional, and central to whether a page can rank.

How it works. Semrush's 2024 study found that pages mismatched to dominant SERP intent rarely break into the top 10 regardless of authority. B2B keywords skew commercial and informational, which means most pipeline pages must teach before they pitch.

Examples. Mapping "HRIS comparison" as commercial-investigation and serving a comparison table, not a product page; treating "what is applicant tracking" as informational and serving a glossary, not a demo CTA; serving a pricing page only for queries that include "pricing" or "cost."

Related terms:

• Keyword ranking
• On-page SEO
• Topical authority

FAQs.

• How do we determine intent? Inspect the current top 10 SERP and match the dominant format.
• Can one page serve multiple intents? Rarely well. Split into separate URLs when intents diverge.
• Does intent change? Yes, especially around product categories and AI shifts. Re-audit quarterly.

Bottom line. Win the query, then keep the buyer reading. Intent mismatch wastes both clicks.

Technical Infrastructure

A page only becomes pipeline-eligible after the crawler can fetch it, the renderer can read it, and the index can store it. These terms describe the systems that gate that eligibility.

Crawl Budget

In B2B, crawl budget is the number of URLs Googlebot will fetch from a domain in a given period, determined by host load capacity and the crawler's perceived value of the site.

Common failure modes. Google notes that crawl budget rarely constrains sites under 1 million URLs. Most B2B sites under 10,000 URLs have a crawl prioritization problem, not a crawl budget problem, caused by faceted navigation, parameterized URLs, and orphaned pages consuming attention that should reach pipeline URLs.

Examples. Blocking faceted filter URLs in robots.txt to redirect crawl attention to product and category pages; using Google Search Console's Crawl Stats report to identify wasted crawl on parameterized URLs; consolidating duplicate paginated archives.

Related terms:

• Indexation
• Robots.txt
• XML sitemap
• Canonical tag

FAQs.

• Do we have a crawl budget problem? Probably not, if you are under 10,000 URLs. You have a prioritization problem.
• How do we check? Google Search Console Crawl Stats and server log analysis.
• Can we increase crawl budget? Indirectly, by improving site speed and reducing low-value URLs.

Bottom line. Stop solving crawl budget. Start solving crawl prioritization toward pipeline-eligible URLs.

Indexation

In B2B, indexation is the process by which search engines store and organize crawled pages in their searchable database, making them eligible to rank for queries.

What to check in GSC. A page must be crawled, rendered, and assessed as worth storing before it enters the index. Crawled-not-indexed and Discovered-not-indexed statuses in Google Search Console's Pages report are the diagnostic signals. A page that is not indexed cannot generate organic traffic, no matter how strong its content.

Examples. Auditing the Pages report to find pipeline URLs stuck in Crawled-currently-not-indexed; removing thin tag archives via noindex to concentrate index quality; resolving canonical conflicts after a CMS migration.

Related terms:

• Crawl budget
• Canonical tag
• XML sitemap
• Rendering

FAQs.

• Why is my page crawled but not indexed? Quality, duplication, or thin-content signals are the common diagnostic paths.
• How fast can we get a page indexed? Submit via URL Inspection. Hours to days for high-quality sites.
• Does every page need to be indexed? No. Utility and gated pages should be noindexed.

Bottom line. Indexation is eligibility. Every week your indexation is broken, your pipeline clock resets.

Core Web Vitals

In B2B, Core Web Vitals are Google's three page experience metrics: Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS), each with a defined threshold.

How it works. The good thresholds are LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1, measured on real-user field data via the Chrome User Experience Report (Search Central, 2024). Core Web Vitals are a ranking signal, weighted modestly against content relevance. The Starr Conspiracy treats Core Web Vitals as a conversion lever first, a ranking lever second.

Examples. Using the Lighthouse CWV report to identify render-blocking JavaScript on a pricing page; deferring third-party scripts to improve LCP on category pages; reserving image dimensions in CSS to eliminate CLS.

Related terms:

• Rendering
• Technical SEO
• SEO audit
• Schema markup

FAQs.

• Is CWV worth engineering time? Yes, on pipeline-eligible URLs where conversion depends on it. No, on archived blog posts.
• What tool gives the real number? CrUX field data, not lab Lighthouse scores.
• Does fixing CWV move rankings? Modestly, when content quality is already competitive.

Bottom line. Fix Core Web Vitals on the URLs that close revenue, not the ones that archive it.

Rendering

In B2B, rendering is the process of converting HTML, CSS, and JavaScript into the final page Googlebot evaluates for ranking and indexation.

How it works. Googlebot uses a two-pass rendering process for JavaScript-heavy sites, which can delay indexation (Search Central, 2024). JavaScript-heavy stacks (Next.js, React) require deliberate decisions about server-side rendering, client-side rendering, or hybrid. Client-side-only content is often invisible to crawlers at scale.

Examples. Switching a Next.js marketing site from CSR to SSR for pipeline pages; using Google Search Console's URL Inspection to compare rendered HTML against source HTML; pre-rendering pricing and comparison pages.

Related terms:

• Core Web Vitals
• Indexation
• Technical SEO
• Crawl budget

FAQs.

• Can Google render JavaScript? Yes, but with delay. SSR is safer for pipeline URLs.
• How do we test rendering? URL Inspection tool, then compare to view-source.
• Does framework choice matter? Yes. Render strategy matters more than framework.

Bottom line. If Googlebot never sees the content, it never ranks. Render strategy is a pipeline decision.

Canonical Tag

In B2B, a canonical tag is an HTML element (rel="canonical") that tells search engines which URL is the preferred version when duplicate or near-duplicate pages exist on a domain.

Common failure modes. Google treats canonicalization signals as hints, not directives. Frequent B2B failure modes include canonical chains, canonicals pointing to redirects, and self-referential canonicals on parameterized URLs. Misconfigured canonicals are a frequent cause of B2B indexation loss after a CMS migration.

Examples. Fixing canonicals on UTM-parameterized URLs to point to clean versions; resolving canonical conflicts between AMP and standard pages; auditing canonicals via Screaming Frog after a replatform.

Related terms:

• Indexation
• XML sitemap
• Crawl budget
• Robots.txt

FAQs.

• Does Google always honor canonicals? No. They are hints. Google may select a different canonical.
• How do we check? URL Inspection shows the Google-selected canonical versus your declared one.
• Self-referential canonical on every page? Generally yes, on a normalized URL.

Bottom line. Canonicals are the most common quiet killer of B2B indexation after a migration.

XML Sitemap

In B2B, an XML sitemap is a structured file listing the URLs you want search engines to crawl and index, submitted via Google Search Console.

How it works. Sitemaps help discovery but do not guarantee indexation (Search Central, 2024). B2B sitemaps should exclude utility pages, gated thank-you URLs, archived content, and noindexed URLs. Include only pages that can earn pipeline.

Examples. Splitting sitemaps by content type (product, solution, blog) to monitor index ratios in Google Search Console; removing 404 and redirected URLs from sitemaps after a quarterly audit; using dynamic sitemaps for content-heavy hubs.

Related terms:

• Indexation
• Robots.txt
• Crawl budget

FAQs.

• How often should sitemaps update? Automatically, on publish.
• Should we submit a sitemap if Google can crawl the site? Yes. It helps Google prioritize.
• Multiple sitemaps? Split by type for diagnostic clarity.

Action. Audit your sitemaps this quarter and strip any URL that isn't pipeline-eligible.

Robots.txt

In B2B, robots.txt is a root-level text file instructing crawlers which paths they may or may not access on a domain.

How it works. Robots.txt controls crawling, not indexation (Search Central, 2024). A page blocked in robots.txt can still appear in the index if Google discovers it through external links. Use noindex meta tags for index control, robots.txt for crawl control.

Examples. Blocking faceted filter parameters to redirect crawl to pipeline URLs; blocking internal search results pages; never using robots.txt to deindex content (use noindex instead).

Related terms:

• Crawl budget
• XML sitemap
• Indexation

FAQs.

• Does robots.txt remove pages from Google? No. Use noindex.
• Can robots.txt block bad bots? Honor-based. Bad bots ignore it.
• Where does it live? At the domain root, /robots.txt.

Bottom line. Robots.txt is for crawl control. Confusing it with index control causes ghost URLs in search results.

Schema Markup

In B2B, schema markup is structured data (typically JSON-LD) added to HTML that helps search engines understand entity relationships and become eligible for rich results in search.

How it works. Schema markup signals entity context and unlocks rich result eligibility (FAQ, How-to, Article, Organization, Product), per Search Central (2024). For B2B, Article, Organization, BreadcrumbList, and DefinedTerm schema are the highest-leverage types for expertise and glossary content.

Examples. Adding DefinedTerm schema to glossary entries; implementing Organization schema with verified social profiles and logo; using BreadcrumbList schema on category pages.

Related terms:

• E-E-A-T
• On-page SEO
• Technical SEO
• Indexation

FAQs.

• Is schema a ranking factor? Not directly. It enables rich results that affect click-through.
• JSON-LD or microdata? JSON-LD, per Google's stated preference.
• Will all schema produce rich results? No. Eligibility varies by type and quality.

Bottom line. Schema turns indexed pages into rich results, which turn impressions into clicks.

On-Page Elements

Once a URL is indexed, on-page elements decide whether it wins the click and holds the buyer. These terms describe the controllable signals inside a single URL.

Title Tag

In B2B, a title tag is the HTML element defining a page's title in search results and browser tabs, capped by Google at roughly 60 characters before truncation.

How it works. Semrush's 2024 research places title tags among the highest-leverage on-page elements for click-through rate, and they remain a direct ranking signal. For B2B, the title tag must lead with the buyer's query language, not internal product taxonomy.

Examples. Rewriting "HRIS Platform | Acme" to "HRIS Comparison for Mid-Market HR Leaders | Acme"; A/B testing title tags via Google Search Console click-through data; front-loading the primary keyword.

Related terms:

• Meta description
• Header tags
• Search intent
• On-page SEO

FAQs.

• Does Google rewrite title tags? Yes, when it judges the tag mismatched to the page or query.
• How long? Roughly 60 characters, but pixel-width matters more than character count.
• Keyword first or brand first? Keyword first for ranking pages, brand first for navigational queries.

Bottom line. The title tag is your one-line pitch in the SERP. Lead with the buyer, not the brand.

Meta Description

In B2B, a meta description is the HTML attribute summarizing a page's content for SERP display, capped at roughly 155 characters before truncation in desktop search results.

How it works. Meta descriptions are not a ranking factor but materially affect click-through rate (Search Central, 2024). Google rewrites descriptions for most queries based on relevance to the searcher.

Examples. Writing descriptions that lead with the buyer outcome, not the product feature; including a clear value proposition under 155 characters; matching description language to dominant query intent.

Related terms:

• Title tag
• Search intent
• On-page SEO

FAQs.

• Worth writing if Google rewrites it? Yes, for the queries Google does not rewrite.
• Optimal length? Under 155 characters.
• Keywords in description? Yes, for bolding and relevance, but write for humans first.

Bottom line. Meta descriptions earn the click. Write them for the buyer reading the SERP.

Header Tags

In B2B, header tags are HTML elements (H1 through H6) that structure page content hierarchically and help crawlers and readers parse topic relationships.

How it works. Header tags signal content hierarchy and topical scope (Search Central, 2024). One H1 per page, descriptive H2s for major sections, H3s for sub-sections. Header structure influences passage indexing and AEO extraction.

Examples. Restructuring a long-form guide with question-based H2s to match People Also Ask queries; using H2s as the table of contents; aligning H1 to the dominant query.

Related terms:

• Title tag
• On-page SEO
• Internal linking

FAQs.

• Multiple H1s? Modern HTML5 allows it, but one H1 per page remains the safest pattern.
• Are headers a ranking factor? They are a structural signal that supports ranking, not a direct factor.
• Should H2s match the title tag? H2s should expand on, not duplicate, the title.

Bottom line. Headers are the outline a scanner skims. If the outline does not promise an answer, the buyer leaves.

Internal Linking

In B2B, internal linking is the practice of connecting pages within a single domain through hyperlinks, distributing authority and signaling topical relationships across a site.

How it works. Internal link distribution is a leading factor in passage ranking and topical authority, per Semrush's 2024 research. For B2B sites, internal links from high-authority hub content to deeper pipeline pages are often the highest-ROI fix in an audit.

Examples. Adding contextual links from a high-traffic blog to underperforming pipeline URLs; building a related-terms mesh across a glossary hub; using descriptive anchor text instead of "learn more."

Related terms:

• Anchor text
• Topical authority
• On-page SEO
• XML sitemap

FAQs.

• How many internal links per page? Enough to be useful, not so many they dilute. No magic number.
• Anchor text best practice? Descriptive and varied, matching the destination's topic.
• Do internal links pass authority? Yes, proportional to source page authority.

Bottom line. Internal links are the cheapest, fastest authority redistribution lever in a B2B audit.

Anchor Text

In B2B, anchor text is the clickable text of a hyperlink, signaling to search engines and readers what the destination page is about.

How it works. Anchor text is a topical relevance signal for the linked page (Search Central, 2024). Descriptive, varied anchors outperform generic "click here" phrasing. Over-optimized exact-match anchors at scale can signal manipulation.

Examples. Replacing "read more" with "B2B SEO audit checklist"; varying anchor phrasing across multiple internal links to the same page; matching anchor text to the destination's H1 intent.

Related terms:

• Internal linking
• On-page SEO
• Topical authority

FAQs.

• Exact-match anchors? Used sparingly. Variation looks natural.
• Image anchors? Alt text functions as anchor text for images.
• Anchor text for external links? Same principle. Descriptive over generic.

Bottom line. Anchor text is a one-line description of what the buyer will get next. Write it that way.

Alt Text

In B2B, alt text is the HTML attribute describing an image for screen readers and search engines, used when the image cannot be displayed.

How it works. Alt text is an accessibility requirement and a ranking signal for image search (Search Central, 2024). For B2B, alt text on diagrams, comparison charts, and product screenshots improves accessibility compliance and image search visibility.

Examples. Describing a comparison chart by its axes and outcome ("HRIS partner comparison by mid-market pricing and integration depth"); leaving decorative images with empty alt attributes; avoiding keyword-stuffed alt text.

Related terms:

• On-page SEO
• Header tags
• Schema markup

FAQs.

• Is alt text required? For accessibility compliance, yes.
• How long? As long as needed to describe the image accurately, typically under 125 characters.
• Decorative images? Empty alt attribute (alt="").

Bottom line. Alt text serves accessibility first, image search second. Both matter.

Measurement and Prioritization

Fixes only matter if you can measure their effect on pipeline. These terms translate technical work into the metrics that defend budget and justify the next quarter's investment. The Starr Conspiracy prioritizes work in this category using an impact-effort-risk rubric.

Organic Traffic

In B2B, organic traffic is the volume of unpaid sessions arriving from search engines, measured in Google Analytics 4 or an equivalent analytics platform.

How it works. Semrush's 2024 study showed organic traffic distribution in B2B concentrates heavily on a small fraction of URLs, which means the meaningful metric is organic traffic to pipeline-eligible URLs, not raw totals. Segment GA4 by landing page and map to pipeline status.

Examples. Building a GA4 exploration that filters organic traffic to a defined set of pipeline URLs; comparing organic sessions to MQL conversion by landing page; reporting organic traffic alongside pipeline-eligible URL count, not as a standalone vanity metric.

Related terms:

• Keyword ranking
• SEO audit
• Topical authority

FAQs.

• Is total organic traffic the right metric? No. Pipeline-eligible organic sessions are.
• How do we attribute traffic to pipeline? Landing page to opportunity match in CRM.
• GA4 or Search Console? Both. GA4 for sessions, Search Console for impressions and clicks.

Bottom line. Total organic traffic is a vanity number. Organic traffic to pipeline-eligible URLs is the number worth defending.

Keyword Ranking

In B2B, keyword ranking is a page's position in search results for a given query, tracked over time as a directional signal of SEO health.

How it works. Keyword positions correlate with click-through rate at known curves (Semrush, 2024), but rankings themselves do not equal revenue. The Starr Conspiracy treats rankings as leading indicators of pipeline, never as the deliverable.

Examples. Tracking a portfolio of 50 pipeline-tied queries weekly via Google Search Console; reporting average position by URL cluster, not by individual query; correlating ranking shifts with pipeline impact rather than reporting them in isolation.

Related terms:

• Organic traffic
• Search intent
• Topical authority

FAQs.

• Position 1 versus position 3? Material click-through difference, but only when intent matches.
• Average position across a portfolio? Useful as a trend, dangerous as a goal.
• Do rankings predict pipeline? For pipeline-tied queries, yes, with a sales-cycle lag.

Bottom line. Rankings are inputs. Pipeline is the outcome. Never report one without the other.

Topical Authority

In B2B, topical authority is a site's perceived expertise on a subject, built through comprehensive, interlinked content coverage of a defined territory.

How it works. Sites with dense topical coverage rank for more long-tail queries within their domain (Semrush, 2024). For B2B, topical authority is the durable moat that compounds over a six-month sales cycle. Build it through hub-and-spoke content architecture with disciplined internal linking.

Examples. Publishing a 22-term glossary as the definitional substrate for every adjacent guide; clustering 8 to 12 articles under a category hub with bidirectional internal links; assigning named practitioner authors across the cluster.

Related terms:

• E-E-A-T
• Internal linking
• Search intent
• On-page SEO

FAQs.

• How long to build topical authority? Two to four quarters of disciplined publishing within a defined territory.
• Breadth or depth first? Depth within a narrow territory, then expand.
• Does volume alone build it? No. Coverage plus interlinking plus E-E-A-T signals.

Bottom line. Topical authority compounds. Scattered publishing does not.

Treat this glossary as the vocabulary layer beneath every audit conversation. The Starr Conspiracy uses these 22 terms to scope diagnostic work, prioritize the fix backlog with CFO-proof logic, and tie every recommendation back to organic pipeline, not vanity rankings.

Use this glossary to: defend SEO budget with pipeline-eligible URL math, triage the fix backlog using impact-effort-risk, and align technical work to the six-month sales cycle. Start with SEO audit, then crawl budget, then indexation, then internal linking.