Product and Category Comparison Guide | CrawlNFix

Compare equivalent public product and category pages, distinguish observed Product/Offer evidence from verified values, and rescan relevant content changes.

Compare public product descriptions and category explanations with equivalent pages from other shops. Use separate runs for product and category intent, and retain source coverage before interpreting a missing phrase.

Quick answer

Select equivalent public pages, enter a small relevant keyword list and place each shop in its own group. Review per-page placement and observed Product/Offer evidence. Make an original change that helps a buyer, then rescan the same URLs.

Why this matters

A category helps visitors choose a product family; a product page explains a particular item and its options. Their word totals and structured types serve different purposes. Comparing mixed collections can produce misleading editorial priorities.

In-depth explanation

Product/Offer evidence has several levels. Observed means a supported type or field was read from supplied markup. Validated means a relevant validator accepted the intended statements. Verified stock or checkout means a separate current business process confirmed those facts. A content comparison only supplies the observed evidence it describes.

Website crawl can discover additional public items, but robots rules, variants, JavaScript-only links and operational budgets affect the sample. If repeatability matters more than discovery, choose known URLs directly. Record selected language and region when pricing or product explanations differ.

Zero exact occurrences means the normalized phrase was absent from the analyzed body blocks. Read the description for equivalent useful wording before editing. A clearly written specification can answer the question without using the research phrase verbatim.

What to check

Record the product family, audience, language and selected variant. Match comparable pages and distinguish product pages from categories.
Use supported product features and buyer questions for the keyword list. Remove unrelated brands and unsupported claims.
Inspect coverage, main-body occurrences and repeated/chrome counts. Read titles, H1, descriptions and URL placement for the affected page.
Review observed Product and Offer schema, price, currency, availability and SKU against the visible product.

Manual fix steps

Start in selected-page mode with two or three equivalent products per shop. Keep category pages in another run.
Put your public URLs in the first group and each competing shop in its own competitor group. Exclude cart, payment, account and token-bearing URLs.
Run the comparison and inspect failures, truncation and source warnings before reading gaps. Use saved rendered HTML when the initial response omits an important description, and label that source.
Choose one relevant buyer question. Add an original answer to the appropriate product or category copy rather than repeating every competitor phrase.
Correct inaccurate structured fields in the platform generator only after confirming the actual product and variant data. Deploy and rescan the same sample.

Verification checklist

Keep the same URLs, phrases and source mode for the repeat comparison. Confirm the intended body, title or heading change on the affected page.
Check that short navigation links did not account for the apparent improvement. Repeated/chrome occurrences are separate.
Validate structured markup with an appropriate validator and compare with the visible selected variant. Checkout, stock and merchant-feed verification require their own evidence.
Download the compact PDF for findings or enable the detailed appendix for every page and keyword placement.

Workflow resources

Common mistakes

Declaring a competitor the winner because its collection contains more pages or words.
Treating a category as one Product merely to match a detected schema type.
Assuming a missing source price proves the product is unavailable.
Copying competitor descriptions or adding a feature the product does not provide.

Practical example

A shop compares three trail-shoe product pages with three equivalent competitor products. Its category explains waterproofing but one product description omits the actual material specification. The editor verifies the specification, adds it to that product and rescans. A competitor subscription promotion is ignored. Offer fields are reviewed separately from the copy decision.

Frequently asked questions

Can the tool verify stock or place an order?

No. It reads public content and observed structured fields. Cart, checkout and private account flows are excluded.

Should product and category pages share one keyword target?

Choose phrases according to each page purpose. Keep equivalent page types together when making editorial comparisons.

Related diagnostic and explanation

Open the related diagnostic tool

Bulk Keyword Comparison Explained