Manchester Blue Special: A Product-Page Data Checklist

A field-by-field case file showing what is present, what is time-sensitive and what still requires verification.

Manchester Blue Special listing evidence inside the required “Smoke Online Cheap” frame. Source packaging remains unaltered.

Audit verdict: usable identity, incomplete publishing record

The Manchester Blue Special listing can be identified from three visible signals: the complete collection-card name, the individual product URL and the retailer-supplied image. The Manchester collection displayed “Manchester Blue Special (10 packets x 20’s)” at AUD $179 when checked on 27 August 2026. These observations are sufficient to locate the product page and interpret the carton notation. They are not sufficient to declare that every product-page field or its structured data is accurate.

The correct editorial outcome is therefore not a generic “page complete” verdict. It is a controlled release decision: identity fields are provisionally supported; price is a dated snapshot; availability requires live confirmation; and image/schema alignment must be inspected on the final page. This article shows exactly how to make that decision and what evidence should be saved.

Audit snapshot

Snapshot source: Manchester collection page, checked 27 August 2026. Dynamic fields may change after this review.

Fields a complete listing should contain

A product page is complete only when a reader, editor and search engine can identify the same item from the same set of facts. For Manchester Blue Special, that means more than having a title and price. The page should expose a reproducible identity record and distinguish durable facts from commercial fields that can change without notice.

The eight-field minimum

• Exact product name: one spelling used in the H1, browser title, breadcrumb and schema name.

• Individual URL: a stable destination whose handle agrees with the visible product name.

• Pack configuration: packets per carton and cigarettes per packet, written without ambiguity.

• Primary image: the retailer-controlled asset associated with this listing, with accurate alt text.

• Price: currency and amount, sourced from the live offer rather than copied into evergreen prose.

• Availability: an explicit state such as in stock, out of stock or preorder—not inferred only from a button.

• Last-checked date: the point at which dynamic fields were verified.

• Evidence owner: the editor or reviewer responsible for approving a change.

Customer-facing copy can be concise; the evidence register should not be. If a field is absent, the audit should record “missing” or “not verified.” Substituting a likely value from another Manchester page would make the record look complete while weakening its reliability.

Name and carton format

The observed collection title contains both the variant name and its carton notation: “Manchester Blue Special (10 packets x 20’s).” That is useful because it answers two separate questions in one line: which catalogue record is being referenced and how the carton is presented. Editors should keep those jobs separate when checking consistency. “Manchester Blue Special” is the identity; “10 packets × 20 cigarettes” is the quantity.

The notation also exposes an editorial risk. Phrases such as “20-pack carton” can be read as either twenty packets or a packet containing twenty cigarettes. The preferred sentence is: “The listing displays 10 packets of 20 cigarettes, totalling 200 cigarettes per carton.” If the H1, description, cart selector or schema contains another quantity, publication should pause until the owner resolves the discrepancy.

Naming acceptance criteria

• H1 and browser title use the same variant name.

• Breadcrumb and collection card point to the same individual URL.

• Image caption and alt text identify Manchester Blue Special—not a neighbouring Manchester variant.

• Pack notation agrees across visible copy, cart controls and structured data.

Price/availability timestamp

On 27 August 2026, the Manchester collection showed AUD $179 for Manchester Blue Special. That figure is a dated observation, not an evergreen product attribute. Price can change because of catalogue updates, stock movements or promotions. A strong article either sends the reader to the live page or labels the figure with the date checked; it never presents a historical amount as permanently current.

Availability needs a separate check. The collection card exposed an add-to-cart control, but interface behaviour is not the same as an explicit inventory statement. A button can be cached, disabled later in the journey or displayed while stock data is changing. The product page and cart response should be checked immediately before publication, and the audit record should store the exact wording observed.

A useful timestamp is four-part

• Date and local time of the check.

• Page or endpoint checked.

• Currency, price and availability wording captured together.

• Name of the editor who performed the verification.

This practice prevents a subtle pattern problem: repeating “price and availability may change” in every article without showing what was actually checked. Here, the article records the observed amount, explains the evidence limitation and defines the next verification action.

Article checkpoints for Manchester Blue Special inside the required “Smoke Online Cheap” frame.

Image and schema consistency

An image is part of the product identity system. The framed asset in this document uses the retailer-supplied source image without altering the package or its statutory warning. The external “Smoke Online Cheap” frame supplies publication branding; it must not cover, recolour or reconstruct the source packaging. The same principle applies on the live product page: the primary image, filename, alt text and structured-data image URL should all refer to the same listing.

Schema consistency cannot be proven from a collection card. The final product page should be inspected for Product data such as name, image, offers, priceCurrency, price and availability. Each value must match visible content. For the blog article itself, BlogPosting and BreadcrumbList are appropriate only after the final headline, URL, image and navigation path are fixed.

Failure conditions

• Product schema names another Manchester variant.

• Schema price or currency differs from the visible offer.

• Image URL resolves to a placeholder, another product or a modified warning image.

• Availability markup conflicts with the page or checkout state.

• Breadcrumb markup sends users to a collection or URL not shown in the interface.

Any one of these failures is enough to hold publication. Structured data is not a place to “complete” missing page information; it should describe the content users can actually see

Frequently asked questions

Which fields should be present on the Manchester Blue Special page?

At minimum: exact name, individual URL, pack configuration, primary image, price, availability, last-checked date and evidence owner. The H1, breadcrumb, cart state and Product schema should describe the same listing.

How often should availability be checked?

Check immediately before publishing or updating any availability statement. Repeat the check whenever the product page, collection card or cart behaviour changes. Record the time, page and exact wording rather than relying on a generic freshness disclaimer.

Should Product schema match visible content?

Yes. The schema name, image, currency, price and availability must agree with what users can see. If the page omits a field, structured data should not invent it.

Does an add-to-cart button prove the item is in stock?

Not by itself. A button is an interface signal, but stock may be resolved later or change quickly. Confirm the explicit page state and cart response before recording availability.

Does “Blue Special” describe taste, strength or lower harm?

No conclusion of that kind follows from the listing name. It is a catalogue identifier. Smoking is harmful to health, and unsupported sensory or reduced-harm claims should not be added.

When is the audit complete?

The audit is complete when the evidence register is dated, all acceptance criteria pass and a real reviewer’s name, credentials, decision and review date are recorded. This draft remains pending expert approval.

Conclusion

The Manchester Blue Special page has enough visible information to identify the listing and interpret its 10 × 20 carton notation, but a publish-ready record requires more than a recognizable title. Price needs a timestamp, availability needs a direct live check, and the image, visible copy and Product schema must agree. The practical value of this audit is its decision trail: each field is either supported, time-limited or held for verification.

Use the Manchester collection for range context, verify the Manchester Blue Special product page as the primary record, and add the related Sapphire Blue Plain identification guide when it is live.