Indexer by DependsiT

Indexification Alternatives That Actually Work

28 min read 5400 words By DependsIt
IndexingTechnical SeoIndexnow
Indexification Alternatives That Actually Work guide diagram with no clutter

If Indexification style drip feeds no longer move your URLs, this indexification alternative guide is for site owners and SEOs who want indexing built on owned signals and official APIs. You will learn why link network pings lost power, which Google paths still work, how IndexNow covers Bing plus partners, how to vet any replacement tool, and how to run a clean migration with measurable crawl gains. By the end you can replace opaque credits with a queue you control, with key files, sitemaps, and logs that show every step. For context on related diagnostics, see IndexNow complete guide for open protocol basics. External method reference used here follows Bing Webmaster submission help.

Key takeaways

  • Start with eligibility: status code, robots, noindex, and canonical must pass before any other work.
  • Group URLs by template and cause instead of treating each URL as a unique case.
  • Strengthen discovery with clean sitemaps and contextual internal links from indexed hubs.
  • Track trends across crawl cycles and validate samples with live tests before scaling fixes.

faded link network nodes replaced by owned sitemap, hub, and key file path

What Indexification style tools do behind the scenes

This stage matters for indexification alternative because engines decide in batches, not one URL at a time. These tools rent third party pages to attract crawlers indirectly. When you understand what indexification style tools do behind the scenes, you stop guessing and start testing. Look at templates, headers, links, and history together. That broader view shows whether the issue is eligibility, demand, quality, or stability, and it points to the smallest fix that moves the largest group. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from crawlers. Prioritize hubs and revenue pages first, then expand

Work through what indexification style tools do behind the scenes in a fixed order so results are comparable across weeks. First confirm the current state with site checks and a live fetch. Then compare the finding against the expected state for canonical, status code, robots, rendering, and links. Then apply one change per cluster and note the date. This loop is how teams turn indexification alternative from a vague worry into a measurable workflow with clear ownership. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals

Apply these checks in order and write down pass or fail for each sample URL.

  • Drip fed tiered pages: verify with live data, note the template, and record the fix owner so follow up stays clear.
  • Ping lists and feeds: verify with live data, note the template, and record the fix owner so follow up stays clear.
  • Credit metering: verify with live data, note the template, and record the fix owner so follow up stays clear.
  • Document status codes, canonical targets, sitemap inclusion, internal inlink counts, and last crawl dates for five to ten samples tied to indexification alternative. Patterns across those samples reveal the shared cause faster than isolated spot checks.

An independent indexification review often reaches the same conclusion: drip fed tiers add discovery noise but little durable demand, so teams shortlist indexification competitors that run on owned signals and official endpoints.

Common mistakes around what indexification style tools do behind the scenes include changing too much at once, trusting cached views, ignoring headers, and resubmitting before eligibility passes. Another frequent error is treating informational statuses as emergencies while real blocks sit untouched. Avoid bulk actions until samples prove the fix. Small tested batches protect budget, keep logs clean, and make cause and effect visible to everyone involved. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from crawlers. Prioritize hubs and revenue

To close this stage, pick one cluster related to indexification alternative, apply the checks above, and monitor for one to two crawl cycles. Watch coverage trends, crawl responses, and last crawl dates. If valid counts rise and excluded clusters shrink, expand the same fix. If nothing moves, regroup by template and revisit quality and link demand before trying again. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from crawlers. Prioritize hubs and revenue pages first,

Why that model struggles with modern filters

This stage matters for indexification alternative because engines decide in batches, not one URL at a time. Engines learn to ignore manufactured tiers that add no value. When you understand why that model struggles with modern filters, you stop guessing and start testing. Look at templates, headers, links, and history together. That broader view shows whether the issue is eligibility, demand, quality, or stability, and it points to the smallest fix that moves the largest group. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from crawlers. Prioritize hubs and revenue pages first, then expand to

Work through why that model struggles with modern filters in a fixed order so results are comparable across weeks. First confirm the current state with site checks and a live fetch. Then compare the finding against the expected state for canonical, status code, robots, rendering, and links. Then apply one change per cluster and note the date. This loop is how teams turn indexification alternative from a vague worry into a measurable workflow with clear ownership. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from

Apply these checks in order and write down pass or fail for each sample URL.

  • Link devaluation at scale: verify with live data, note the template, and record the fix owner so follow up stays clear.
  • Duplicate thin tiers: verify with live data, note the template, and record the fix owner so follow up stays clear.
  • No ownership proof: verify with live data, note the template, and record the fix owner so follow up stays clear.
  • Document status codes, canonical targets, sitemap inclusion, internal inlink counts, and last crawl dates for five to ten samples tied to indexification alternative. Patterns across those samples reveal the shared cause faster than isolated spot checks.

Common mistakes around why that model struggles with modern filters include changing too much at once, trusting cached views, ignoring headers, and resubmitting before eligibility passes. Another frequent error is treating informational statuses as emergencies while real blocks sit untouched. Avoid bulk actions until samples prove the fix. Small tested batches protect budget, keep logs clean, and make cause and effect visible to everyone involved. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from crawlers. Prioritize hubs and revenue pages

To close this stage, pick one cluster related to indexification alternative, apply the checks above, and monitor for one to two crawl cycles. Watch coverage trends, crawl responses, and last crawl dates. If valid counts rise and excluded clusters shrink, expand the same fix. If nothing moves, regroup by template and revisit quality and link demand before trying again. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from crawlers. Prioritize hubs and revenue pages first,

This stage matters for indexification alternative because engines decide in batches, not one URL at a time. Owned paths tie each hint to a verified property and real change. When you understand google paths that work without link schemes, you stop guessing and start testing. Look at templates, headers, links, and history together. That broader view shows whether the issue is eligibility, demand, quality, or stability, and it points to the smallest fix that moves the largest group. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from crawlers. Prioritize hubs and revenue pages first, then

Work through google paths that work without link schemes in a fixed order so results are comparable across weeks. First confirm the current state with site checks and a live fetch. Then compare the finding against the expected state for canonical, status code, robots, rendering, and links. Then apply one change per cluster and note the date. This loop is how teams turn indexification alternative from a vague worry into a measurable workflow with clear ownership. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from

Apply these checks in order and write down pass or fail for each sample URL.

  • Verified sitemaps and lastmod: verify with live data, note the template, and record the fix owner so follow up stays clear.
  • Hub links that pass demand: verify with live data, note the template, and record the fix owner so follow up stays clear.
  • API for JobPosting and BroadcastEvent: verify with live data, note the template, and record the fix owner so follow up stays clear.
  • Document status codes, canonical targets, sitemap inclusion, internal inlink counts, and last crawl dates for five to ten samples tied to indexification alternative. Patterns across those samples reveal the shared cause faster than isolated spot checks.

Common mistakes around google paths that work without link schemes include changing too much at once, trusting cached views, ignoring headers, and resubmitting before eligibility passes. Another frequent error is treating informational statuses as emergencies while real blocks sit untouched. Avoid bulk actions until samples prove the fix. Small tested batches protect budget, keep logs clean, and make cause and effect visible to everyone involved. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from crawlers. Prioritize hubs and revenue pages

To close this stage, pick one cluster related to indexification alternative, apply the checks above, and monitor for one to two crawl cycles. Watch coverage trends, crawl responses, and last crawl dates. If valid counts rise and excluded clusters shrink, expand the same fix. If nothing moves, regroup by template and revisit quality and link demand before trying again. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from crawlers. Prioritize hubs and revenue pages first,

rented drip feed node paths compared against owned sitemap, hub, and key paths

IndexNow coverage for Bing and participating engines

This stage matters for indexification alternative because engines decide in batches, not one URL at a time. One validated batch notifies all participants at once. When you understand indexnow coverage for bing and participating engines, you stop guessing and start testing. Look at templates, headers, links, and history together. That broader view shows whether the issue is eligibility, demand, quality, or stability, and it points to the smallest fix that moves the largest group. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from crawlers. Prioritize hubs and revenue pages first, then expand to secondary sections

Work through indexnow coverage for bing and participating engines in a fixed order so results are comparable across weeks. First confirm the current state with site checks and a live fetch. Then compare the finding against the expected state for canonical, status code, robots, rendering, and links. Then apply one change per cluster and note the date. This loop is how teams turn indexification alternative from a vague worry into a measurable workflow with clear ownership. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from

Apply these checks in order and write down pass or fail for each sample URL.

  • Single POST fan out: verify with live data, note the template, and record the fix owner so follow up stays clear.
  • Key file trust: verify with live data, note the template, and record the fix owner so follow up stays clear.
  • Quota friendly batches: verify with live data, note the template, and record the fix owner so follow up stays clear.
  • Document status codes, canonical targets, sitemap inclusion, internal inlink counts, and last crawl dates for five to ten samples tied to indexification alternative. Patterns across those samples reveal the shared cause faster than isolated spot checks.

Common mistakes around indexnow coverage for bing and participating engines include changing too much at once, trusting cached views, ignoring headers, and resubmitting before eligibility passes. Another frequent error is treating informational statuses as emergencies while real blocks sit untouched. Avoid bulk actions until samples prove the fix. Small tested batches protect budget, keep logs clean, and make cause and effect visible to everyone involved. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from crawlers. Prioritize hubs and revenue pages

To close this stage, pick one cluster related to indexification alternative, apply the checks above, and monitor for one to two crawl cycles. Watch coverage trends, crawl responses, and last crawl dates. If valid counts rise and excluded clusters shrink, expand the same fix. If nothing moves, regroup by template and revisit quality and link demand before trying again. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from crawlers. Prioritize hubs and revenue pages first,

curl -s -o /dev/null -w "%{http_code}" https://www.indexnow.org/documentation

How to vet any indexification alternative tool

This stage matters for indexification alternative because engines decide in batches, not one URL at a time. Ask where keys live, what logs you get, and which endpoints are called. When you understand how to vet any replacement indexing tool, you stop guessing and start testing. Look at templates, headers, links, and history together. That broader view shows whether the issue is eligibility, demand, quality, or stability, and it points to the smallest fix that moves the largest group. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from crawlers. Prioritize hubs and revenue pages first,

Work through how to vet any replacement indexing tool in a fixed order so results are comparable across weeks. First confirm the current state with site checks and a live fetch. Then compare the finding against the expected state for canonical, status code, robots, rendering, and links. Then apply one change per cluster and note the date. This loop is how teams turn indexification alternative from a vague worry into a measurable workflow with clear ownership. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from

Apply these checks in order and write down pass or fail for each sample URL.

  • Key ownership check: verify with live data, note the template, and record the fix owner so follow up stays clear.
  • Log transparency check: verify with live data, note the template, and record the fix owner so follow up stays clear.
  • Allowlisted endpoint check: verify with live data, note the template, and record the fix owner so follow up stays clear.
  • Document status codes, canonical targets, sitemap inclusion, internal inlink counts, and last crawl dates for five to ten samples tied to indexification alternative. Patterns across those samples reveal the shared cause faster than isolated spot checks.

Common mistakes around how to vet any replacement indexing tool include changing too much at once, trusting cached views, ignoring headers, and resubmitting before eligibility passes. Another frequent error is treating informational statuses as emergencies while real blocks sit untouched. Avoid bulk actions until samples prove the fix. Small tested batches protect budget, keep logs clean, and make cause and effect visible to everyone involved. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from crawlers. Prioritize hubs and revenue pages

To close this stage, pick one cluster related to indexification alternative, apply the checks above, and monitor for one to two crawl cycles. Watch coverage trends, crawl responses, and last crawl dates. If valid counts rise and excluded clusters shrink, expand the same fix. If nothing moves, regroup by template and revisit quality and link demand before trying again. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from crawlers. Prioritize hubs and revenue pages first,

Migration playbook from drip feeds to owned queues

This stage matters for indexification alternative because engines decide in batches, not one URL at a time. Keep the old feed for two weeks while the new queue proves faster crawls. When you understand migration playbook from drip feeds to owned queues, you stop guessing and start testing. Look at templates, headers, links, and history together. That broader view shows whether the issue is eligibility, demand, quality, or stability, and it points to the smallest fix that moves the largest group. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from crawlers. Prioritize hubs and revenue

Work through migration playbook from drip feeds to owned queues in a fixed order so results are comparable across weeks. First confirm the current state with site checks and a live fetch. Then compare the finding against the expected state for canonical, status code, robots, rendering, and links. Then apply one change per cluster and note the date. This loop is how teams turn indexification alternative from a vague worry into a measurable workflow with clear ownership. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals

Apply these checks in order and write down pass or fail for each sample URL.

  • Baseline current discovery: verify with live data, note the template, and record the fix owner so follow up stays clear.
  • Build validated queue: verify with live data, note the template, and record the fix owner so follow up stays clear.
  • Compare and cutover: verify with live data, note the template, and record the fix owner so follow up stays clear.
  • Document status codes, canonical targets, sitemap inclusion, internal inlink counts, and last crawl dates for five to ten samples tied to indexification alternative. Patterns across those samples reveal the shared cause faster than isolated spot checks.

To replace indexification safely, run the old feed and the new queue in parallel for one full crawl cycle. A modern indexing service should beat tiered link networks on receipts and first crawl dates, not on promises.

Common mistakes around migration playbook from drip feeds to owned queues include changing too much at once, trusting cached views, ignoring headers, and resubmitting before eligibility passes. Another frequent error is treating informational statuses as emergencies while real blocks sit untouched. Avoid bulk actions until samples prove the fix. Small tested batches protect budget, keep logs clean, and make cause and effect visible to everyone involved. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from crawlers. Prioritize hubs and revenue

To close this stage, pick one cluster related to indexification alternative, apply the checks above, and monitor for one to two crawl cycles. Watch coverage trends, crawl responses, and last crawl dates. If valid counts rise and excluded clusters shrink, expand the same fix. If nothing moves, regroup by template and revisit quality and link demand before trying again. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from crawlers. Prioritize hubs and revenue pages first,

migration workflow from drip feed baseline to owned queue with parallel comparison

Tracking wins by template and engine

This stage matters for indexification alternative because engines decide in batches, not one URL at a time. Report per template so content and commerce teams see real value. When you understand tracking wins by template and engine, you stop guessing and start testing. Look at templates, headers, links, and history together. That broader view shows whether the issue is eligibility, demand, quality, or stability, and it points to the smallest fix that moves the largest group. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from crawlers. Prioritize hubs and revenue pages first, then expand to

Work through tracking wins by template and engine in a fixed order so results are comparable across weeks. First confirm the current state with site checks and a live fetch. Then compare the finding against the expected state for canonical, status code, robots, rendering, and links. Then apply one change per cluster and note the date. This loop is how teams turn indexification alternative from a vague worry into a measurable workflow with clear ownership. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from crawlers.

Apply these checks in order and write down pass or fail for each sample URL.

  • Submitted to crawled rate: verify with live data, note the template, and record the fix owner so follow up stays clear.
  • Indexed after 21 days: verify with live data, note the template, and record the fix owner so follow up stays clear.
  • Cost per crawled URL: verify with live data, note the template, and record the fix owner so follow up stays clear.
  • Document status codes, canonical targets, sitemap inclusion, internal inlink counts, and last crawl dates for five to ten samples tied to indexification alternative. Patterns across those samples reveal the shared cause faster than isolated spot checks.

Common mistakes around tracking wins by template and engine include changing too much at once, trusting cached views, ignoring headers, and resubmitting before eligibility passes. Another frequent error is treating informational statuses as emergencies while real blocks sit untouched. Avoid bulk actions until samples prove the fix. Small tested batches protect budget, keep logs clean, and make cause and effect visible to everyone involved. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from crawlers. Prioritize hubs and revenue pages first,

To close this stage, pick one cluster related to indexification alternative, apply the checks above, and monitor for one to two crawl cycles. Watch coverage trends, crawl responses, and last crawl dates. If valid counts rise and excluded clusters shrink, expand the same fix. If nothing moves, regroup by template and revisit quality and link demand before trying again. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from crawlers. Prioritize hubs and revenue pages first,

FAQ

What replaces Indexification most directly?

A validated queue that sends changed canonical URLs to IndexNow for Bing plus partners and to sitemaps plus internal links for Google replaces drip feeds most directly. Unlike tools like indexification that rent third party pages, a validated queue uses your own key file, so every ping carries ownership and freshness instead of third party noise. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from crawlers. Prioritize hubs

Safety depends on what the network does. Mass tiered links with thin pages add spam risk without durable gains. Owned signals like sitemaps, hub links, and IndexNow carry no such risk because they use official channels and verified ownership. Any link indexing alternative worth keeping must show per URL logs and use allowlisted endpoints. In an indexification vs owned queue comparison, score accepted rate and crawled within 72 hours, then stop the loser. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from crawlers. Prioritize hubs and

Can free tools match paid indexing services?

For many sites yes, because the costly part is not the ping but the hygiene around it. A small script plus CMS hooks, accurate sitemaps, and hub links often match paid feeds on discovery time. Compare indexification price against one time build plus light maintenance, then choose the path to better link indexing with the clearest audit trail. As an indexing network alternative, owned queues keep key control with you. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from crawlers. Prioritize hubs

Does IndexNow help Google if I stop Indexification?

IndexNow does not submit to Google because Google does not support the protocol. It helps Bing, Yandex, Naver, Seznam, and other participants. For Google, rely on sitemaps with accurate lastmod, internal links from indexed hubs, and the Indexing API only for eligible JobPosting and BroadcastEvent pages. Track each engine separately. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from crawlers. Prioritize hubs and revenue pages first, then expand to secondary

How long does migration take?

Most small sites migrate in one to two weeks, including key hosting, queue setup, sitemap cleanup, and hub link fixes. Larger catalogs need three to four weeks for deny lists, batch tuning, and dashboard wiring. Run old and new paths in parallel for at least one full crawl cycle so comparison data is fair. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from crawlers. Prioritize hubs and revenue pages first,

What metric proves the alternative works?

Use submit to first crawl within 72 hours plus index status after 21 days, segmented by template. If accepted pings lead to faster crawls while content and links stay constant, the alternative works. If crawls lag, fix depth, canonicals, speed, and sitemap accuracy before increasing volume. Record the finding with dates and sample URLs so later reviews can tie changes to coverage movement. Group similar pages by template because one shared header or setting often explains many rows at once. Check both raw HTML and rendered output because scripts and headers can hide signals from crawlers. Prioritize hubs and revenue pages first, then expand to secondary sections once the pattern

Sources

Further reading

Put this into practice. Indexer submits URLs to the Google Indexing API and IndexNow, audits coverage with Search Console, and shows exactly which pages are indexed. Start free or see how it works.

Related reading