Generation and approval workflow
- Ingest source data server-side and retain observed_at, fetched_at, source URL, unit, region, schema version, and quality status.
- Run validation for missing values, unit changes, duplicates, implausible moves, stale observations, provider-schema changes, and source conflicts.
- Generate a draft with factual deltas only. The system may propose an explanation, but it must not invent causation or predict a property's development.
- Queue the draft for a named Royalty Ridge editor. High-impact legal, tax, regulatory, or financial claims require the appropriate qualified reviewer.
- Publish with source links, as-of times, a 'What this may mean for owners' section, limitations, and a correction mechanism.
- Send alerts only to opted-in users whose chosen region or topic matches the issue. Preserve unsubscribe and delivery records.
Issue template
This week’s three owner signals
Three concise, source-dated observations. Each states what changed, where, the comparison period, and the source.
Prices
WTI and Henry Hub with units, observed times, weekly deltas, and a reminder that benchmark prices differ from realized royalty-statement prices.
Drilling and completions
Rigs, frac spreads, permits, and DUCs with regional coverage and plain-English limitations.
Production and operator watch
New source releases, operator filings, acquisitions, or material events relevant to selected basins.
What this may mean for mineral owners
Original Royalty Ridge analysis framed as questions: Does the change affect your county, operator, unit, product, or timing? What evidence would confirm relevance?
One action for this week
Examples: reconcile a statement, verify a division-order decimal, save a county alert, or update an inherited-property inventory.
Sources and methodology
Direct links, observation dates, refresh cadence, revisions, and corrections.
Example editorial language
This week’s drilling and price indicators provide context, not a property forecast. A change in national rigs or basin completion activity matters only when it connects to the operator, county, formation, unit, and timing relevant to an owner’s interest. Royalty Ridge will show the source and date behind each number and will label data that is delayed, revised, or incomplete.
Royalty Ridge takeaway The brief should earn trust by explaining uncertainty. The brand contribution is the owner-focused interpretation and the connection to useful tools—not a recycled headline or an unsupported prediction.
Editorial and CMS requirements for every article
- One H1; unique title, meta description, canonical URL, author, qualified reviewer when needed, published date, materially updated date, and change note.
- A 40-60 word direct answer, three to six key takeaways, worked example or checklist, authoritative sources, related tool/data page, and contextual CTA.
- State-specific claims labeled by state. Never present one state's law, reporting method, or regulator process as national.
- Live modules server-render a latest-known snapshot with source and as-of time. The page remains useful when JavaScript or an upstream API fails.
- No blind full-text syndication. Use source metadata and canonical outbound links; add original Royalty Ridge analysis. Respect terms, copyright, and robots restrictions.
- No fake urgency, guaranteed value, guaranteed drilling, or appraisal language. Clearly disclose when Royalty Ridge may seek to acquire an interest.
- Link each article to the next owner task: calculator, well search, regional page, downloadable checklist, alert, or optional confidential review.
Final pre-publication checklist
- Article title and URL match the approved content map.
- All facts, formulas, examples, and source links have been checked.
- Time-sensitive numbers are supplied by a live module, not embedded in evergreen prose.
- State-law, title, tax, lease, and valuation statements received the required review.
- Direct answer, takeaways, next action, limitations, and CTA are present.
- No confidential owner data appears in analytics, URLs, or public page source.
- Mobile, keyboard, screen-reader, contrast, print, and structured-data checks pass.
- Article schema, breadcrumbs, internal links, sitemap, canonical, Open Graph, and 404 behavior are validated.
- The content remains genuinely useful if the reader never submits a lead form.