Product-page content: what we read, and what we don't judge.
Is the title right, is the pack size right, is the listing complete? Rewalto records what each listing shows on each app, with the page address and time. Checks against a content standard, such as image and bullet counts, are in build, and we never give a compliance verdict.
Your content is on somebody else’s page
On a shopping app the title, the pack size, the images and the description are shown by the retailer, from the data you supplied and the data it holds. Over time they drift: a pack size is wrong, a title loses the variant, a listing loses an image.
The first step is a record of what the page actually shows, by app and date. That is what Rewalto does today. Judging it against a standard is a second step, and it is in build.
What the listing shows
Title, brand, pack, price and MRP, as displayed, not cleaned up.
Against your catalogue
A file you can check against your own product data.
The source
The page address, the time it was read and the text the figure came from.
Price and how to buy
How Rewalto does it
- STEP 1
You choose the products
Your products and the apps you sell on. We match each to its listing.
- STEP 2
We record the listing
For each app and pin code we record the title, brand, pack size, price, MRP and stock as displayed, with the page address and time.
- STEP 3
You compare and act
Download the file, compare it with your own catalogue, and send any mismatch with its source to whoever owns the listing.
Which fields the record holds, from real readings
For each reading, a filled square is a field we read. It is a picture of what Rewalto reads, and it makes no judgement of whether the copy is good.
Brand and product names are invented, and this is a capture, not a live reading.
What a listing row looks like
The title and pack are stored exactly as the retailer showed them. These are real readings under an invented brand name.
| Title | App | Pack | Brand |
|---|---|---|---|
| Sample Co Hydrating Face Wash, 100 ml | Blinkit | 100 ml | Sample Co |
| Sample Co Vitamin C Face Wash, 100 ml | Blinkit | 100 ml | Sample Co |
| Sample Co Daily Moisturiser, 100 ml | Zepto | 100 ml | Sample Co |
| Sample Co Anti-Dandruff Hair Wash, 200 g | Tata 1mg | 200 g | Sample Co |
Real readings from captured retailer pages. The brand and product names are invented. Not a client's data.
What you can check today
By comparing the file with your own data.
A wrong pack size or title
Both are stored as the app displayed them. A mismatch with your catalogue is a row you can find and send.
A missing MRP
A listing with no MRP is recorded as missing, never as a zero, so it stands out in the file.
Your own site's readiness
The former site audit checked crawler access, structured data and page speed. It is no longer offered.
What we measure today, and what is still in build
Checked against the feed schema and the signals list. Where a row says In build or Not offered, we do not claim it.
| What | Status today | What that means |
|---|---|---|
| Title, brand, pack size, price and MRP as displayed | Live | Stored as the retailer showed them, by app and pin code, with the source. |
| Your own website: crawler access, structured data, speed | Not offered | The former site audit is no longer offered. Explore available data for current coverage. |
| Images on a listing | Partial | The image field is read on only some apps so far, so we do not count images or judge them. |
| Bullets, description length and a category standard | In build | Not in service. It needs a category benchmark computed from real listings first. |
| A completeness figure per listing | In build | A count of which fields are present. It would say what we read, not whether the copy is good. |
| A compliance verdict | Not offered | Whether content meets a marketplace's or a regulator's rules is not ours to say. We show what the page said and when. |
Where to go next
- Guide: the digital shelf auditHow to check what a shopper sees for your products, step by step.
- Free listing-content graderGrade your title, image count, bullets and description length against the category median.
- Explore available dataReview available data, its sources and usage conditions.
- The data catalogueEvery dataset Rewalto sells, with its sources, coverage and the date it was last measured.
- Digital shelf analyticsPrice, MRP and stock by app and pin code.
- Ratings and reviewsRating, rating count and review count by app, pin code and day.
- API documentationRead the supported API operations and authentication requirements.
Questions before you start
Does Rewalto check my product-page content against a standard?
Not yet. We read what a listing shows (title, brand, pack size, price, MRP and whether it is in stock) and record it. Checks on image count, bullet points and description length against a category standard are in build and are not in service.
Will you tell me my listing is compliant?
No. A verdict on whether content meets a marketplace's rules, or a regulator's, is not ours to give. We show what the listing said and when, with the page address, so your team or your counsel can judge it.
Can you spot a wrong title, pack size or MRP on a retailer's app?
We record the title, pack size and MRP as the retailer displayed them, without cleaning them up, so a mismatch with your own catalogue is something you can find by comparing the file. We do not yet flag it for you.
What about my own website?
The former site audit checked crawler access, structured data and loading speed. That service has been withdrawn. The audit did not read shopping apps.
Do you change anything on a listing?
No. Rewalto only reads. It never edits a retailer's listing. The earlier site audit service is no longer offered.
Start with your own site.
The former site audit is no longer offered. For available commerce records, explore the catalogue. Explore commerce data or book an enterprise call.