Stable review dates
A page date changes after a material factual, source or methodology review—not every build.
MATERIAL UPDATES
What changed, when it changed, and why.
The changelog records changes that affect a player's interpretation of a tool or a crawler's understanding of a page. Routine deployments and styling adjustments are not presented as content freshness.
Editorial review
Visible model changes
Tax, formulas, source feeds and estimate logic are recorded when they affect results.
Functional releases
New calculators, routes and saved decision workflows belong in the public history.
01
25 July 2026 — Wyrmscraig release cluster and navigation signals
Published a separately localized OSRS Wyrmscraig landing page for English, Brazilian Portuguese and Latin American Spanish. Each page covers the July 29 release, Sailing and Fallen From Grace requirements, Mortimer, Mad Angel, Golem Crafting and Goat Hunting while separating official pre-release facts from measurements that require the live update.
Added CORE, NEW and HOT navigation badges for Calculators, Wyrmscraig and Monopoly, connected Wyrmscraig to site search, llms.txt, canonical hreflang metadata and the sitemap. The full audit now covers 411 reachable URLs with no thin, orphan, weak-keyword or near-duplicate pages.
- 3 localized Wyrmscraig landing pages
- Calculators CORE, Wyrmscraig NEW and Monopoly HOT
- 411 audited sitemap URLs
- Zero thin, orphan or duplicate-intent pages
02
25 July 2026 — original DPS example and contextual-link release
Added a reproducible Giant Mole worked example to the flagship OSRS DPS Calculator. The example and interactive calculator now call the same shared standard-DPS function, so the displayed hit chance, max hit, DPS and time-to-kill comparison cannot drift into a separate editorial claim.
Added localized, context-selected decision links across all detail pages, explicit related-article maps, a visible editorial author link and expanded BlogPosting/WebPage authorship data. The link audit confirms all 408 sitemap URLs remain reachable from each language home within two clicks, with no orphan pages.
- Shared formula powers the calculator and worked example
- Contextual links across nine topic clusters
- 408 reachable sitemap URLs and zero orphan pages
- Visible organization author and editor signals
03
24 July 2026 — production launch hardening
Added consent-gated Google Analytics 4 integration, optional Search Console meta verification, canonical host and HTTPS redirects, production security headers and a launch configuration checker. Analytics remains disabled until a valid Measurement ID is configured and the visitor accepts the localized consent panel.
Published independent Privacy, Cookies, Terms and Contact pages in every supported locale. The pages explain local tool storage, public Hiscores lookups, host logs, analytics boundaries, correction reports and the independent fan-content relationship without inventing a production contact address.
- 12 new localized trust URLs
- 405 intended indexable URLs in the sitemap
- GA4 page views without player names or calculator inputs
- CSP, HSTS and canonical-host enforcement
04
24 July 2026 — OSRS DPS calculator and category-page release
Added a localized two-loadout OSRS DPS Calculator for standard Melee, Ranged and Magic comparisons. The page exposes accuracy, damage, Prayer, stance, attack speed, target defence, hit chance, max hit, DPS, time to kill and manual setup cost while keeping special attacks and encounter-specific effects outside the result.
Repositioned the home and calculator hub around OSRS tools, OSRS calculators and the flagship DPS workflow. Replaced sparse English category heroes with complete, intent-specific introductions for Market, Planner, Quests, Gear, Bosses, Money, Diaries and Hiscores.
- 9 standalone OSRS calculators
- 3 localized DPS calculator URLs
- Complete English hero copy across 9 tool categories
- 393 intended indexable URLs in the sitemap
05
24 July 2026 — localized OSRS editorial blog
Added an independent Blog hub and six source-linked editorial guides about Grand Exchange prices, GE tax, XP calculations, GP-per-hour estimates, Achievement Diary priority and official Hiscores interpretation.
Each topic now has a separately localized English, Brazilian Portuguese and Latin American Spanish article with its own slug, metadata, canonical, reciprocal hreflang, BlogPosting schema, visible review date, sources, FAQ and related-tool path.
- 3 localized Blog hubs
- 18 localized article URLs
- One informational keyword intent per article
- 390 indexable URLs in the sitemap
06
24 July 2026 — full localization and GEO trust release
Completed 123 indexable URLs in each of English, Brazilian Portuguese and Latin American Spanish: 369 localized pages in total, including 108 detail pages per language. Every page keeps independent metadata, H1 copy, canonical URLs and reciprocal hreflang annotations.
Added a visible editorial review block, material review dates, direct source citations and expanded home-page structured data for the publisher, page, tool directory and visible FAQ. No person, credential, testimonial or affiliation was invented for scoring.
- 369 localized indexable URLs
- 123 URLs and 108 detail pages per language
- Visible methodology, source and changelog links
- Organization, CollectionPage, ItemList and FAQPage structured data
07
23 July 2026 — search cluster expansion
Expanded the OSRS GE Tracker to 50 mapped items with real price, time, volume, membership and buy-limit fields. Added focused F2P, beginner, AFK and PvM money-making intent pages.
Added eight formula-based OSRS calculators, six high-value boss readiness pages, a 12-region Achievement Diary tracker and official Regular, Ironman, Hardcore Ironman and Ultimate Ironman Hiscores lookups.
- 50 tracked Grand Exchange items
- 8 standalone OSRS calculators
- 12 Achievement Diary region pages
- Four official Jagex Hiscores modes with honest error states
08
22 July 2026 — evidence and trust release
Added page-specific interpretation, comparison tables, visible sources, reviewed dates and data-status labels to every market, planner, quest, gear, boss and money detail page.
Added About, Methodology, Sources and Changelog pages. Shortened search titles while preserving descriptive H1 headings, expanded structured data with citations and stable modification dates, and added descriptive page visuals.
- 39 existing content URLs reviewed
- 31 detail tools receive unique evidence modules
- Stable sitemap dates replace deployment timestamps
09
22 July 2026 — English content expansion
Expanded the original seven English tool pages with focused item, skill, quest, gear, boss and money detail routes plus an Old School RuneScape on Steam setup guide.
Added static generation, per-page metadata, breadcrumbs, FAQ content, internal directories and sitemap coverage for the new routes.
10
21 July 2026 — first working prototype
Released the English-first LootPath interface with market, planner, quests, gear, bosses and money sections. Established server-rendered content, responsive layouts, accessibility checks and the visual design system.
HOW TO READ THIS PAGE
Use the policy at the point where a decision is made
OSRS DPS Calc changelog — The changelog records material changes to OSRS DPS Calc tools, formulas, live-data boundaries, localized content, structured data and source coverage. It separates a meaningful review from an ordinary styling or deployment timestamp.
Use it to determine whether an older calculation or recommendation should be run again. Entries should name the affected cluster, explain the changed assumption or output and point to the working page where the new behaviour is visible. Stable review dates, Visible model changes, Functional releases.
A deployment does not prove that every OSRS fact was reviewed that day. Page-level reviewed dates change only when the relevant data, mechanic, formula, source or interpretation receives a material check.
A calculator entry should identify the formula or input boundary that changed and whether previous results can differ.
A market entry should distinguish feed, caching, tax, volume and presentation changes because each affects interpretation differently.
A localization entry should record new search intent, terminology or region-specific guidance rather than describing a literal translation.
SEO and discovery work belongs in the history when it changes canonicals, hreflang, sitemap coverage, structured data or the unique landing-page map; it must not be presented as a game-data review.
OPERATIONAL PROMISES
What each principle requires in a working OSRS tool
A principle matters only when its effect is visible in the interface, evidence trail or missing-data behaviour.
Stable review dates
A page date changes after a material factual, source or methodology review—not every build.
Apply this principle to the nearby result, reviewed date, status and source. If the page cannot show how the promise works, clarify the claim before it influences an account decision.
Visible model changes
Tax, formulas, source feeds and estimate logic are recorded when they affect results.
Apply this principle to the nearby result, reviewed date, status and source. If the page cannot show how the promise works, clarify the claim before it influences an account decision.
Functional releases
New calculators, routes and saved decision workflows belong in the public history.
Apply this principle to the nearby result, reviewed date, status and source. If the page cannot show how the promise works, clarify the claim before it influences an account decision.
REVIEW CHECKPOINTS
Four questions to ask before trusting a result
The answer should be visible on the landing page or one clearly linked methodology or source page.
Identify Jagex data, community market signals, a deterministic formula, reviewed reference or illustrative model.
Read inputs and exclusions. A bounded correct answer can still be wrong when applied to a different question.
Separate live request time from editorial review. Market signals age faster than stable formulas.
Use the in-game GE for fills, official services for accounts and current references before risking GP or time.
PAGE GOVERNANCE
A published policy needs an owner, a trigger and a visible correction path
This page is reviewed as part of the same system as the calculators and guides. The review is not complete merely because the page renders, contains a recent date or reaches a target word count. It must still describe the current implementation, use language a player can understand and lead to a practical action when the statement is wrong.
Search engines and AI systems should be able to identify the same relationship a player sees: this page states a defined policy or editorial process; linked tools apply it; page-specific evidence supports it; and the Contact and Changelog pages provide a correction trail. That structure is more useful than repeating a brand or keyword without operational detail.
The review outcome for “What changed, when it changed, and why.” must stay consistent across five places: the title promise, the H1 topic, the search description, the sections 25 July 2026 — Wyrmscraig release cluster and navigation signals, 25 July 2026 — original DPS example and contextual-link release, 24 July 2026 — production launch hardening, and the related-page links. If one changes without the others, the page can mislead a player or compete with another landing page. A correction should update the shared source of truth, preserve the change history and request a new Google crawl only after the published version is verified.
Scope owner
The page owner checks that the title, main heading, description and body describe one primary topic. Related subjects can be linked, but they should not quietly expand the promise beyond what the current product, data source or contact process can support.
A calculator entry should identify the formula or input boundary that changed and whether previous results can differ.
Material review trigger
A review is required when a data provider, formula, analytics configuration, hosting behaviour, account-link process, legal purpose or public contact route changes. Styling, dependency updates and routine deployments do not by themselves prove that the policy content was rechecked.
A market entry should distinguish feed, caching, tax, volume and presentation changes because each affects interpretation differently.
Evidence record
The reviewed date, linked source, visible interface state and changelog entry should agree. If a live implementation differs from this text, the discrepancy is treated as a correction task rather than hidden behind a broad disclaimer or an automatically refreshed timestamp.
A localization entry should record new search intent, terminology or region-specific guidance rather than describing a literal translation.
Localized parity
English, Brazilian Portuguese and Latin American Spanish pages share the same product boundary but are reviewed as separate landing pages. Each version keeps official OSRS terminology where players need it and explains the surrounding obligation, risk and next step in locally natural language.
SEO and discovery work belongs in the history when it changes canonicals, hreflang, sitemap coverage, structured data or the unique landing-page map; it must not be presented as a game-data review.
TRACE THE CLAIM
Move from summary to supporting detail
These sections establish the page-specific scope. Continue into the full text whenever an exception matters.
25 July 2026 — Wyrmscraig release cluster and navigation signals
What it establishes: Published a separately localized OSRS Wyrmscraig landing page for English, Brazilian Portuguese and Latin American Spanish. Each page covers the July 29 release, Sailing and Fallen From Grace requirements, Mortimer, Mad Angel, Golem Crafting and Goat Hunting while separating official pre-release facts from measurements that require the live update.
How to use it: A calculator entry should identify the formula or input boundary that changed and whether previous results can differ.
25 July 2026 — original DPS example and contextual-link release
What it establishes: Added a reproducible Giant Mole worked example to the flagship OSRS DPS Calculator. The example and interactive calculator now call the same shared standard-DPS function, so the displayed hit chance, max hit, DPS and time-to-kill comparison cannot drift into a separate editorial claim.
How to use it: A market entry should distinguish feed, caching, tax, volume and presentation changes because each affects interpretation differently.
24 July 2026 — production launch hardening
What it establishes: Added consent-gated Google Analytics 4 integration, optional Search Console meta verification, canonical host and HTTPS redirects, production security headers and a launch configuration checker. Analytics remains disabled until a valid Measurement ID is configured and the visitor accepts the localized consent panel.
How to use it: A localization entry should record new search intent, terminology or region-specific guidance rather than describing a literal translation.