Editorial Standards

PetroEyes is an energy market research site, not a brokerage or a live terminal. This page explains how bylines work, how we handle sources, where forecasts stop being facts, and how readers can request corrections.

How A Page Is Checked

  • Figures are taken from the cited primary source or from the site's own data files, which are copies of those sources.
  • A build check fails if a data file's refresh date is older than the newest observation in it, so a page cannot print a refresh date earlier than the data it describes.
  • A content quality check is run on the built site before changes go live.
  • Corrections are logged publicly at /corrections/.
  • Pages whose data is modeled or cannot be verified are withdrawn from search: they stay reachable at their own address but carry a noindex tag and are left out of the sitemap.

Deep dives, topic hubs and price and data pages show a "Published" date and, only when a substantive checked edit was made after publication, a "Last reviewed" date. Most country pages, and a few data pages such as the gas price comparison, were imported before the site's current page history began and have no true publication date on record; they show the "Last reviewed" date only, and we do not invent a "Published" date for them. The gas price comparison also shows a "Data through" date, because its figures run later than its last review. Edits to layout, wording or links to other pages do not change the "Last reviewed" date.

Source And Verification

PetroEyes prefers primary and reputable sources for market claims, including EIA datasets, Baker Hughes rig counts, IEA and OPEC reports, company filings, and official policy releases.

Sources are named in the text of each page, with the date they were checked where that matters. A claim that cannot be traced to a named source is left out or labelled as an illustration.

Bylines

Pages are published under the site-level byline "PetroEyes Research". It is a site attribution, not an individual: the site does not list named authors, editors, or reviewers, and it does not claim personal credentials for anyone.

We do not invent credentials to make a page sound more authoritative.

Independence & Objectivity

PetroEyes does not sell favorable coverage, publish sponsored energy-stock recommendations, or promise readers a trading edge. Pages should distinguish reported data from interpretation and interpretation from speculation.

When an article includes a forecast, readers should be able to identify what would prove that forecast wrong and which source categories matter most to the thesis.

Corrections And Review Log

Energy data gets revised, and markets move faster than static pages do. Every correction to a published page is listed, with its date, on the corrections log.

If you believe a page contains a factual error, email hello@petroeyes.com or see the contact page, and include the page URL plus the specific claim or figure you want reviewed.

Automation And AI Use

PetroEyes may use automation for data collection, formatting, and visualization support. That is different from treating generated text as publish-ready by default.

Pages that feel thin, generic, or unsupported should be revised or archived rather than left in the public index. That standard applies whether the draft started with code, notes, or an AI tool.

Check Dates And What Gets Indexed

Every statistic in a long-form explainer is tied to a named source and the month we last checked it, written in the text as, for example, "EIA Refinery Capacity Report, checked October 2026". When a figure cannot be traced to a primary or official publisher, it is left out or shown as a labeled illustration with its inputs stated. A page's "Last reviewed" date moves only when its facts were actually rechecked, not when the layout changes.

Search engines are offered only pages that meet a depth floor for their type. Long-form explainers and news analysis need about 3,000 words of sourced, original material. Hubs, data pages and country or topic pages are shorter and are not held to that long-form floor; they are offered to search engines only when they carry at least 600 words of their own content specific to that page. Pages below the floor stay on the site at their own URL, but carry a noindex tag, are left out of the XML sitemap, and are not linked from navigation or from indexable pages until they are expanded. That rule lives in one place in the site's code, so the robots tag and the sitemap cannot disagree.

Last Updated: November 11, 2026

Questions About Standards Or Corrections?