Skip to content
Check a story, free

Galley · story grade

Your story, graded

52 / 100
https://questionofcities.org/the-prosperous-and-the-poor-in-the-private-city-of-gurugram/
Fix this firstThe headline is too long; Google cuts it off. Desk · 2 min

Quality against reach

Quality is what the page shows of the reporting: byline, named sources, depth. Reach is how well it is set up to travel: timing, demand for the topic, the site's standing. Read it as a guide to where effort pays, not a traffic forecast.

Potential
51
Quality
79
Reach
35
44 pt · held back

Quality 79, reach 35: good journalism that is not set up to travel · low potential

Where it can be found

Discover
31
Google News
72
Google Search
80

For your desk

Changes an editor or reporter makes in the CMS.

The headline is too long; Google cuts it off.

Why it matters to readers. Readers see a clipped headline and can't tell what the story is about.

Desk · 2 min

→ Write an SEO headline under 65 characters; the page headline can stay.

The summary is too long; Google cuts it off.

Why it matters to readers. Readers see an unfinished sentence under your headline.

Desk · 2 min

→ Trim the SEO description to under 155 characters.

Some photos have no description for blind readers.

Why it matters to readers. Screen-reader users hear nothing where the photo is.

Desk · 2 min each

→ Fill in each photo's alt text: one sentence on what it shows.

No named expert or official is quoted.

Why it matters to readers. Readers want to see who stands behind the facts.

Desk · depends

→ If the story makes claims, quote a named person with their role.

For your web team

Site changes. Most are made once and fix every story.

The share picture is too small for a large card.

Why it matters to readers. Readers on Discover get a thumbnail they scroll past.

Web team · 1 hour

→ Use a featured photo at least 1200 pixels wide.

For your web team
Technical term
og:image width ≥ 1200px
What to change
Point og:image at the full-size image, not a thumbnail.
Example
<meta property="og:image" content="https://example.com/story-1200x675.jpg">
How to check it's fixed
View source, search og:image, open it: the picture should be ≥1200px wide.

13 of 18 checks passed.

Send to your web team

Every web-team item, as one checklist to copy, email or print.

For the web team — https://questionofcities.org/the-prosperous-and-the-poor-in-the-private-city-of-gurugram/

[ ] 1. consent-management platform (CMP)  (once for the whole site; 1 day)
    Problem: Trackers load with no sign of a consent banner.
    Change: Add a consent platform that holds trackers until the reader agrees.
    Example: Load the analytics tag only after the consent platform reports agreement.
    How to check it's fixed: Open the site in a private window: a consent banner should appear before anything else.

[ ] 2. og:image width ≥ 1200px  (once for the whole site; 1 hour)
    Problem: The share picture is too small for a large card.
    Change: Point og:image at the full-size image, not a thumbnail.
    Example: <meta property="og:image" content="https://example.com/story-1200x675.jpg">
    How to check it's fixed: View source, search og:image, open it: the picture should be ≥1200px wide.

Email it

Topic and tags

Topic:

Built environment

Tell me if this changes

Frontmatter, our companion tool, re-checks up to five of your stories every week and emails you only when something moves, so you can see whether a fix worked. Free.

Watch this story with Frontmatter →

Where to go next

Galley looks at one story. These look further:

Frontmatter →
After publication: finds the stories whose quality outran their reach.
Dispatch →
How your channels carry your stories.
The Audit →
The whole masthead in one view, not one story at a time.

All OnlineJourno tools →

Graded by Galley · onlinejourno.com

That was one story.

After publication, Frontmatter goes through everything you publish with the same checks and finds the stories whose quality outran their reach.

See Frontmatter →