We Said the Last 5 Points Weren't Worth It. Then We Looked at What They Were.

Pueblo Catering's site scored 95 out of 100 on a deep crawl in June. Fifteen pages straight from the sitemap, zero critical issues.

We wrote at the time that we were not going to chase the last five points, because the remaining work was worth more than the score. That was the right instinct and the wrong conclusion, and it is worth showing why.

What the five points actually were

We had never looked closely at them. When we did, here is what was costing the score:

Four of those five points were not vanity points. They were the content work we already owed the client.

A gallery with 53 words shows the food and explains nothing: not the event, not the service, not the menu behind it. An about page with 176 words does not tell a family in Pueblo who is cooking. Those were real gaps, and the scanner happened to be pointing at them.

Only the /menus meta description was a pure score fix. One line, 203 characters trimmed to 153.

So we did the work. We expanded the gallery, the reviews page, and the about page with real copy, and we shortened the meta description.

Where it landed

The deep scans, in order: 83, 95, 95, 99, 98.

Today the site is 98 out of 100, an A+, with all fifteen pages healthy and zero issues. Coverage is 100 percent on H1 tags, meta descriptions, canonicals, and schema.

We are not going to pretend the last two points were a strategy. The score went to 99 and settled at 98, and the fact that it moves a point on its own is a decent argument against treating any of this as a finish line.

The last two points are one page, and it is short on purpose

Content coverage sits at 93 percent. Fourteen of the fifteen pages clear 300 words. One does not.

It is the reviews page, at 289 words. Eleven words short.

We are leaving it there.

Pueblo Catering is a new family catering business. It does not have a wall of reviews yet, because it has not catered enough events yet. The honest version of that page says so, invites people who have already hired them to leave a review, and explains what the family works to earn every time they cook. It is a genuine empty state.

We could pad it. Eleven words is nothing. We could also fabricate a few testimonials and switch on the Review and AggregateRating schema the page is already built to support, and the score would go to 100 tomorrow.

We are not doing either. Google's guidelines disallow self-serving review markup, and inventing customer quotes for a business that is still earning its first ones is not a thing we are willing to do for two points on a report we generate ourselves.

When Nick has real reviews, they go on the page, the schema goes live, and the word count takes care of itself. Until then, the page is honest and the score is 98.

What this actually taught us

Our original argument was that the last five points were not worth chasing. That was wrong in the specifics. Four of them were real content gaps, and the audit found them.

But the underlying instinct still holds, just not where we first pointed it. The score was never the thing to protect. It was a reasonably good pointer at work that needed doing, right up until the moment it started asking us to pad a page or fake a testimonial.

That is where an audit tool stops being useful and starts being something you have to argue with. A scanner cannot tell the difference between a page that is thin because nobody wrote it and a page that is thin because there is nothing honest to say yet. Only a person can do that.

Sites drift, so we keep scanning. We have written before about how one footer link produced 48 audit warnings on our own site, run by people who do this for a living. Holding a 98 is not doing nothing.

But the growth work now sits entirely outside the score: real event photography as it comes in, the questions people actually ask before booking a caterer, how much food to order, what a taco bar includes, what changes the price, and getting those first real reviews.

A 100 on a checklist does not book a single event. A page that answers a real question for a real person in Pueblo does.

See where your own site stands

Run the free audit on your site. It loads your pages in Chromium and inspects the rendered result, it is free, and there is no signup, so the report is yours to keep.

Then argue with it. When it tells you a page is thin, read the page and decide whether the tool is right. Sometimes it is pointing at work you owe. Sometimes it is asking you to pad something that is fine. Knowing the difference is the job, and no scanner does it for you.

If you would rather read it together, book a free 15-minute teardown and we will walk through what it found, no pitch.