Mousa Batarseh Reviews01
Public pages only
No logins, no scraping behind walls, no private data. If a shopper or a crawler can’t see it, it isn’t in the review.
Four steps,
the same way every time
Every review on this site was made this way: public pages only, every claim dated, and a working fix at the end. Here’s the whole process.
The toolkitcurlPlaywrightChrome DevToolsSearch ConsoleGA4LighthouseSchema validatorRich Results TestGoogle SheetsJSON-LDSitemap parserPython
0reviews made this way
0checks in the playbook
0products checked by script
0days, start to finish
01Crawl
curl -s site.com/sitemap.xmlgrep -c 'application/ld+json'189 URLs · 44 redirects02Evidence
observed 2026-09-20 23:20 UTCcurl -I /llms.txt → 404[E3] 15-word template03Prototype
title-linter.js · 59 listingsstore-page generatorspecies atlas · 300+ species04Plan
week 1 · templateweeks 2–3 · channelsweek 4 · speed & content01 · Crawl
Read it like a machine
Sitemap, robots, canonicals, titles, schema and prices, pulled from the public HTML the way a crawler or an answer engine sees it. Nothing behind a login.
02 · Evidence
Date every claim
Every finding carries the date, the URL and the check behind it, so anyone can re-run it and see if it’s been fixed. Opinions don’t go in; observations do.
03 · Prototype
Build the fix
A scanner, a template, a rewritten page or a working browser. Something a team can use on Monday, not a list of recommendations.
04 · Plan
Sequence the work
A 30/60/90 plan that puts template fixes first, because one template change usually fixes hundreds of pages at once.
The playbook36 checks,
36 checks,
six families
Not every check runs on every site. These are the ones that found the problems in the reviews on this site.
Pricing & promos6
- Price on page vs cart
- Bundle rules that conflict
- Deal % named vs configured
- Expired promos still live
- Contest dates and rules
- Volume ladders
Structured data6
- JSON-LD on key templates
- Product, FAQPage, Organization
- LocalBusiness and store schema
- GTIN and MPN in Product
- Review counts that agree
- llms.txt and AI signals
Indexing & crawl6
- Canonicals to the right host
- Sitemap returns XML
- Staging or test pages indexed
- Redirects left in sitemaps
- Duplicate titles and descriptions
- Confirmation pages indexable
Catalog data6
- Encoding artifacts in names
- Facet values split by spelling
- Sold-out products still published
- Duplicate listings and handles
- Attributes leaking into titles
- Identifiers and SKUs
Local & store data6
- Name, address, phone agree
- Hours across three sources
- tel: links that work
- Placeholder numbers indexed
- Store pages that exist
- Status: open vs coming soon
Launch & speed6
- Domains connected
- Password or parked pages
- Analytics tags present
- Mobile LCP and CLS
- Help-center coverage
- Go-live gate you can click
AnatomyFive parts of
Five parts of
every finding
- 1Title
A plain sentence that names the defect, not the category.
- 2Evidence
Where it was seen and the exact values, copied from the page or schema.
- 3Date
When it was observed, so it can be re-checked later.
- 4Impact
Why a shopper, a crawler or the revenue team would care.
- 5Fix
The smallest change that closes it, usually at the template.
Pricingjarscannabis.com · Lansing
Two prices for the same seven-cart bundle
At Lansing, 14 products carry both 7/$80 Cartridges 2g and 7/$90 Cartridges 2g at once; at Ann Arbor, 11 (Mitten Extracts “Super Nurdz”, “Rainbow Sherbert”, “Blueberry Pie” cartridges among them). Same quantity, two totals, one product.
Observed Sep 20, 2026Impact One bundle, two prices at checkout
Fix One bundle rule per product set, checked by a deal-conflict scanner before launch.
12345TimelineTwo days,
Two days,
start to finish
Day 1 · morning
Crawl
Sitemap, robots, templates, schema and prices pulled and counted.
Day 1 · afternoon
Evidence
Findings written, dated and sourced. Anything unproven is cut.
Day 2 · morning
Prototype
The scanner, template or working browser that proves the fix.
Day 2 · afternoon
Plan & publish
A 30/60/90 plan, then the review goes live as its own site.
DeliverablesWhat every review
What every review
hands over
Five things, every time. The tool is the part most reviews skip.
01
Findings site
A standalone review site with every finding, dated.
02
A working tool
Scanner, linter, generator or browser built for that site.
03
Rewrites
Titles, descriptions, schema or copy, ready to paste.
04
30/60/90 plan
What to fix first, second and third.
05
Evidence log
Every claim with its date, source and re-run command.
RulesFour rules
Four rules
every review follows
02
Template before page
One template fix usually beats a hundred page fixes. Findings are grouped by the template that causes them.
03
Numbers over adjectives
“43 sold-out products still published” instead of “inventory issues”. Every figure is counted, not estimated.
04
Dated and re-runnable
Each claim ships with the date and the check behind it, so it can be verified or closed later.
FAQs
About the reviews and how they’re made.
What is a review here?
A short, independent study of one company’s live website. I crawl the public pages, record every finding with its date and the URL or command behind it, and build a working fix: a scanner, a template, a rewritten page or a 90-day plan.
Did these companies hire you?
No. Each review is unsolicited and made from public pages only. No logins, no private data, and no affiliation with the companies named.
How long does one take?
Most are built in one to two days. The crawl and evidence come first; the prototype and the plan come after the findings are checked.
Why is every figure dated?
Websites change. Every number carries the date it was observed, so anyone can re-check it and a fixed issue is easy to tell apart from an open one.
Can you review my site?
Yes. Send the URL and what the site needs to do better. The first findings come back dated and sourced, with one working fix.
Want one for
your site?
Send a URL. You’ll get the first findings back, dated and sourced.
- Dated, sourced findings
- One working fix, built for your site
- Public pages only, no logins