On this page
- RNX-960.T001 · Visible-content agreement
- RNX-960.T002 · Supported feature selection
- RNX-960.T003 · Required property coverage
- RNX-960.T004 · Rich-result observation separation
- RNX-960.T005 · Product variant identity
- RNX-960.T006 · Product offer freshness
- RNX-960.T007 · Merchant policy clarity
- RNX-960.T008 · Publisher article attribution
- RNX-960.T009 · Regulated-content expert review
- RNX-960.T010 · Marketplace seller separation
- RNX-960.T011 · Authenticated-content boundary
- RNX-960.T101 · Stable merchant item identifiers
- RNX-960.T102 · Assigned GTIN integrity
- RNX-960.T103 · Manufacturer part identity
- RNX-960.T104 · Product brand attribution
- RNX-960.T105 · Identifier absence assertion
- RNX-960.T106 · Variant group membership
- RNX-960.T107 · Explicit variant-identifying options
- RNX-960.T108 · Direct variant preselection
- RNX-960.T109 · ProductGroup canonical model
- RNX-960.T110 · Feed landing checkout price agreement
- RNX-960.T111 · Preorder and backorder semantics
- RNX-960.T112 · Feed required-field and format validation
- RNX-960.T113 · Feed processing reconciliation
- RNX-960.T114 · Merchant shipping declaration agreement
- RNX-960.T115 · Merchant return declaration agreement
- RNX-960.T116 · Author entity disambiguation
- RNX-960.T117 · Article representative image
- RNX-960.T118 · Paywall free-access declaration
- RNX-960.T119 · Paywall selector alignment
- RNX-960.T120 · Intended paywall crawler access
- RNX-960.T121 · News sitemap recency window
- RNX-960.T122 · News sitemap required metadata
- RNX-960.T123 · Publisher accountability disclosure
- RNX-960.T124 · Sponsored editorial disclosure
RNX code library · 35 controls
RNX-960Specialized Content and Search Feature Eligibility
Read what these checks mean, why they matter and which evidence they concern. Each ID below keeps its canonical place in the RNX hierarchy.
These are free learning summaries, not full technical tests or an industry certification. Specialized checks apply only to the relevant feature. Experimental labels are preserved from the canonical source.
RNX-960.T001
Visible-content agreement
core readiness
Keep structured data consistent with what readers can access.
Why it matters. Hidden claims should not promise an offer absent from the page.
Illustration — fictional. Machine-readable product data says in stock while the visible page says sold out.
When it applies. Inspected target: feature markup fact set. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T002
Supported feature selection
core readiness
Check that the requested search feature supports this kind of page.
Why it matters. Having markup does not make every page eligible for every feature.
Illustration — fictional. A report promises a special Google result merely because a vocabulary contains a matching label.
When it applies. Inspected target: selected provider feature. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T003
Required property coverage
core readiness
Supply truthful values for a supported feature's required fields.
Why it matters. Inventing a missing value defeats the purpose of the label.
Illustration — fictional. A product page seeks a supported search feature but omits a required truthful product field.
When it applies. Inspected target: feature-specific required-property set. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T004
Rich-result observation separation
Experimental — not an established ranking requirement
Separate valid markup, eligibility and actual appearance in a special search result.
Why it matters. Passing one stage does not prove the next.
Illustration — fictional. A markup checker passes, and the report wrongly counts that as an actual appearance in a special search result.
When it applies. Inspected target: rich-result reporting record. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T005
Product variant identity
core readiness
Keep distinct product versions correctly identified.
Why it matters. A customer choosing a size or color must receive information about that version.
Illustration — fictional. The link for a medium blue shirt opens the large red shirt instead.
When it applies. Inspected target: catalog variant. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T006
Product offer freshness
core readiness
Keep published stock availability aligned with the business's current inventory policy.
Why it matters. An old offer can invite an order you cannot fulfill.
Illustration — fictional. An item remains labeled in stock after it sells out and the allowed update period passes.
When it applies. Inspected target: inventory offer. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T007
Merchant policy clarity
core readiness
Make relevant buying policies accessible and accurate.
Why it matters. Shipping, returns and other terms affect whether an offer is suitable.
Illustration — fictional. Offer says free returns but its applicable policy charges a fee.
When it applies. Inspected target: offer policy. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T008
Publisher article attribution
core readiness
State an article's real author and truthful dates.
Why it matters. Readers need to distinguish new reporting from an old piece with a refreshed label.
Illustration — fictional. Template advances modification date without substantive revision.
When it applies. Inspected target: article attribution. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T009
Regulated-content expert review
Experimental — not an established ranking requirement
Use an accountable, qualified reviewer when professional claims require one.
Why it matters. A sensitive claim needs suitable expertise, not just confident wording.
Illustration — fictional. A changed dosage claim keeps an old review label even though nobody reviewed the change.
When it applies. Inspected target: professional claim. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T010
Marketplace seller separation
Experimental — not an established ranking requirement
For marketplaces, identify who actually supplies the offer.
Why it matters. The platform and the seller may have different responsibilities.
Illustration — fictional. A marketplace describes itself as the seller of a product actually supplied by a separate merchant.
When it applies. Inspected target: seller offer. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T011
Authenticated-content boundary
Experimental — not an established ranking requirement
Protect restricted content while describing its public preview honestly.
Why it matters. A preview should not imply free access that does not exist.
Illustration — fictional. A login overlay hides the screen, but the private information can still be fetched without an account.
When it applies. Inspected target: protected resource. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T101
Stable merchant item identifiers
core readiness
For product feeds, keep each merchant item identifier stable under the declared rules.
Why it matters. Changing it unnecessarily can break the product's history and matching.
Illustration — fictional. New product reuses retired item ID.
When it applies. Inspected target: feed item identity. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T102
Assigned GTIN integrity
core readiness
Use an assigned trade identifier only when it genuinely belongs to that product.
Why it matters. A made-up barcode number can match the wrong item.
Illustration — fictional. A made-up valid-looking barcode is assigned to a product.
When it applies. Inspected target: assigned trade identifier. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T103
Manufacturer part identity
core readiness
Use the correct manufacturer part number where applicable.
Why it matters. A retailer's own stock code should not masquerade as the maker's identifier.
Illustration — fictional. A reseller's internal stock code is used in place of the manufacturer's part number.
When it applies. Inspected target: manufacturer part number. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T104
Product brand attribution
core readiness
Attribute the product to its real brand.
Why it matters. Naming the shop as the brand can misidentify goods made by someone else.
Illustration — fictional. A compatible third-party part is labeled as though the original equipment maker produced it.
When it applies. Inspected target: brand field. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T105
Identifier absence assertion
core readiness
Claim an identifier is absent only when that is true under the feed's rules.
Why it matters. An unknown identifier is not automatically a nonexistent one.
Illustration — fictional. A product with an assigned trade identifier is marked as having none to avoid a validation error.
When it applies. Inspected target: identifier absence record. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T106
Variant group membership
core readiness
Group actual variants of the same product together.
Why it matters. Unrelated items should not share a variant family simply because they look similar.
Illustration — fictional. Related accessories grouped as size variants.
When it applies. Inspected target: variant group. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T107
Explicit variant-identifying options
core readiness
State the options that distinguish product variants.
Why it matters. Missing size or color details can make two offers impossible to tell apart.
Illustration — fictional. One part of a feed calls a shirt medium while another calls the same variant large.
When it applies. Inspected target: variant option set. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T108
Direct variant preselection
core readiness
Make a variant link open the advertised version.
Why it matters. A shopper clicking a red shirt should not silently land on the blue one.
Illustration — fictional. Blue variant URL defaults to red item.
When it applies. Inspected target: variant URL. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T109
ProductGroup canonical model
core readiness
Keep a product group's preferred-page model consistent with its real page structure.
Why it matters. Machines need to distinguish the group from its individual variants.
Illustration — fictional. Separate product versions all name an unrelated first variant as their preferred equivalent.
When it applies. Inspected target: product-group page. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T110
Feed landing checkout price agreement
core readiness
Align the price in the feed, landing page and checkout under the applicable price rules.
Why it matters. A customer should not discover an unexplained higher price at payment.
Illustration — fictional. A feed advertises a price of 19 dollars, but the same offer becomes 29 dollars at checkout.
When it applies. Inspected target: price representation. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T111
Preorder and backorder semantics
core readiness
Describe preorder and backorder availability accurately.
Why it matters. Future availability must not look like an item ready to ship now.
Illustration — fictional. Released out-of-stock item called preorder without expected date.
When it applies. Inspected target: future-availability offer. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T112
Feed required-field and format validation
core readiness
Supply required product-feed fields in the provider's accepted format.
Why it matters. A useful catalog still cannot be processed if mandatory data is missing.
Illustration — fictional. A provider's required availability value is replaced with unsupported free-form wording.
When it applies. Inspected target: feed row. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T113
Feed processing reconciliation
Experimental — not an established ranking requirement
Compare submitted catalog items with processing results.
Why it matters. Sending a file does not prove every item was accepted.
Illustration — fictional. Successful upload is reported as all items accepted.
When it applies. Inspected target: processed catalog batch. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T114
Merchant shipping declaration agreement
core readiness
Keep shipping declarations consistent with the actual offer and provider settings.
Why it matters. Wrong charges or delivery terms can mislead buyers.
Illustration — fictional. Structured shipping promises free delivery in unsupported region.
When it applies. Inspected target: shipping declaration. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T115
Merchant return declaration agreement
core readiness
Keep return declarations aligned with the real policy.
Why it matters. A feed should not promise returns the store will refuse.
Illustration — fictional. A final-sale item is labeled as having a thirty-day return policy that does not apply to it.
When it applies. Inspected target: return declaration. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T116
Author entity disambiguation
core readiness
Identify an article's actual author distinctly.
Why it matters. Similar names should not mix one writer's work with another's.
Illustration — fictional. Two different article authors are combined into a single person's name.
When it applies. Inspected target: article author. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T117
Article representative image
core readiness
Use a representative, suitable article image.
Why it matters. An unrelated or inaccessible picture gives a poor account of the story.
Illustration — fictional. Logo is sole representative image of unrelated reported event.
When it applies. Inspected target: article image. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T118
Paywall free-access declaration
core readiness
Declare paid access honestly where the publisher's markup calls for it.
Why it matters. A subscription article should not falsely appear wholly free.
Illustration — fictional. Subscriber-only article marked free.
When it applies. Inspected target: paywall declaration. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T119
Paywall selector alignment
core readiness
Make paywall labels point to the sections actually restricted.
Why it matters. Labeling the wrong area misstates what readers can access.
Illustration — fictional. The paywall label points to a section that does not exist, missing the actual restricted text.
When it applies. Inspected target: paywall section. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T120
Intended paywall crawler access
core readiness
Check the intended crawler access for paywalled content under the provider's rules.
Why it matters. A broken boundary can either hide intended content or expose private material.
Illustration — fictional. Owner intends paid content indexed but crawler receives empty login shell.
When it applies. Inspected target: crawler content boundary. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T121
News sitemap recency window
core readiness
For a news sitemap, keep entries within the provider's allowed recency window.
Why it matters. An old article should not be presented as newly published news.
Illustration — fictional. Month-old article remains in news extension as newly published.
When it applies. Inspected target: news sitemap entry. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T122
News sitemap required metadata
core readiness
Include accurate required news-sitemap details.
Why it matters. Publication identity and dates help distinguish a real article from a misleading entry.
Illustration — fictional. A news sitemap uses its own upload time as the article's publication date.
When it applies. Inspected target: news sitemap document. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T123
Publisher accountability disclosure
core readiness
Disclose who publishes the material and how they can be contacted.
Why it matters. Readers need someone accountable for the publication.
Illustration — fictional. Anonymous publication has no company or contact identity.
When it applies. Inspected target: publisher identity. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-960.T124
Sponsored editorial disclosure
core readiness
Clearly disclose sponsored editorial content.
Why it matters. Readers should know when payment helped place an article.
Illustration — fictional. Paid sponsor feature appears as independent reporting.
When it applies. Inspected target: sponsored article. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.