simplemaplab

Editorial Policy

By Marko Visic · Updated Nov 21, 2026

SimpleMapLab is run by Marko Visic, an independent operator. No advertiser relationship shapes the content, and there is no “sponsored partner” section. This page describes how content is researched, written, fact-checked and corrected, how AI is used, and how the content stays independent of the display ads that pay for the site.

Editorial mission

SimpleMapLab exists to make open and public geographic data usable by non-specialists, through free tools and sourced studies. Editorial decisions are made against four commitments:

  1. Specificity over vagueness. Where data exists for a real number, we use it. Where it doesn't, we say so.
  2. Sourced over asserted. Every factual claim should trace to a dataset, an official document or a published method named on the page. A claim we can't source comes off the page.
  3. Transparent over polished. Limitations, uncertainty and method choices are stated where the finding is, not in fine print.
  4. Useful over viral. A page exists because it answers a real question. We won't add a tool, a study or a blog post that is only there for keyword coverage.

Who writes the content

Marko Visic is SimpleMapLab's developer and editor and decides what it publishes. There is no contributor program, no freelance pool and no guest-posted content. Long-form prose (tool descriptions, blog posts, study narratives) is drafted with the help of large language models, as the AI disclosure below explains, and then reviewed, fact-checked and edited before publication.

How we write and verify content

A page goes from research and an outline to a draft, a fact-check against primary sources, an edit and publication. Facts, figures, place names and sources are checked against primary data before a page goes live, and published pages are audited again later. What those checks catch is fixed and listed on the corrections page.

AI assistance disclosure

We use Anthropic's Claude to draft text, write code and check pages against their sources. We disclose this because readers should know how the content is produced, and because Google's guidance on AI-generated content (Google Search Central, February 8, 2023) suggests an AI disclosure wherever readers would reasonably expect one.

What AI is used for on SimpleMapLab:

What AI is not used for:

Marko Visic decides which studies to publish, how a finding is framed, what the method notes and corrections say, how press questions are answered and what to leave out. He is responsible for every claim on the site, whatever produced the first draft.

Sourcing standards

Every factual claim on the site should trace to one of these source classes:

We don't source from listicle blogs, Reddit threads, Quora answers, or AI summaries of any of the above. If a fact needs a citation, we cite the primary source directly.

Editorial process per content type

Tool pages (70 currently published)

  1. Identify the task the tool addresses: what someone is searching for when they need it.
  2. Build the tool. The calculation is the source of truth, not the prose.
  3. Write the "How to use this tool" section and 4 to 6 worked examples with named places and specific numbers.
  4. Write the method notes (the formula, the data source, the accuracy bound), pointing to the Methodology page where relevant.
  5. Write the FAQ (typically 8 to 12 questions) and the technical reference table.
  6. Link related tools.
  7. Test the tool's main paths at phone and desktop widths before publishing.

Open-data studies (3 currently published)

  1. Identify a real research question that open data can answer.
  2. Compute the results with a script that turns the input data into a JSON file; the same inputs always give the same output. The coastline study instead tabulates NOAA's published figures.
  3. Check the top entries against an independent source, such as Census tables or the relevant agency's reports.
  4. Write the hub page with the headline finding, ranked tables, per-state grid and method.
  5. For the two ZIP-code studies, write the per-state pages: a few carry written historical context, the rest are built from each state's data.
  6. Publish the results as JSON and CSV under CC BY 4.0 and link them from the page's Schema.org Dataset markup.
  7. Review the top 20 entries once more to confirm the headline finding holds.

Blog posts (10 long-form posts)

Each blog post answers one question (for example, "how many counties in each US state" or "the largest US counties by area") with sourced data tables and links to the relevant tools. Posts are factual and topical, not listicles. They are revised when a reader reports a possible error or the underlying data changes.

What we don't do

Corrections policy

When a reader, a journalist or our own re-check finds a mistake, the workflow is:

  1. Verify. Confirm the error against the underlying source data. Sometimes a reported error turns out to be a method choice we should explain better; sometimes it's a real bug.
  2. Fix at the source. Update the data file, the script or the prose, whichever is the root cause, and rerun any dependent pipelines.
  3. Publish the fix. Rebuild the affected pages and deploy.
  4. Log the correction. Add an entry to the corrections page with the date, what the page said and what it says now. The page's “Updated” date moves only when its content changes, not for wording or design edits.
  5. Reply to the reporter. Thank them and explain what was wrong and what we fixed.

To report a possible correction: email hello@simplemaplab.com with "Correction:" in the subject line, the page URL, the value you think is wrong and, ideally, a source. We respond within 1–3 business days; fixes typically publish within 48 hours of confirmation.

Editorial independence and advertising

SimpleMapLab is supported by display advertising. Raptive, the site's ad network, decides where the ads sit on a page and serves them; we don't choose which ads appear. Marko Visic has no editorial relationship with individual advertisers, no advance knowledge of which ads will run on which pages, and no incentive to write content favorable to specific advertiser categories.

Concretely, this means:

Affiliate and partnership disclosure

SimpleMapLab does not currently run affiliate links, sponsored content or paid partnerships. If that changes, for example through an affiliate relationship with a hardware or software company relevant to the site's topic, this section will be updated, affiliate links will carry the rel="sponsored" attribute that Google asks for on paid links, and the page itself will carry an inline disclosure.

Conflict of interest

Marko Visic has no financial stake in any product, service or organization discussed on the site, apart from the site's own income from display ads served by Raptive. SimpleMapLab is not affiliated with the US Census Bureau, the OpenStreetMap Foundation, the National Park Service, USGS, Google, or any other agency or provider whose data we use. The tools and studies use their data but are independent of them and not endorsed by them.

Sources and external links

When we cite an external source (a government agency, an open-source project, an academic paper), we link to the primary source, not to an aggregator or summary. Outbound links are not affiliate or referral links.

Voice and style

Pages are written to be useful, not breathless. Concrete claims with named places and specific numbers outweigh adjectives. We avoid:

We try to write like a colleague who knows the data well and is helping you find what you need fast.

Update cadence

Reader trust signals (how to verify the above)

Ways to check what this page says:

Questions

Questions about how content is produced, sources we use, or how we'd handle a specific edge case: hello@simplemaplab.com, or the Contact page.