About PetrolPrice.co.za

Writer Brief for About PetrolPrice.co.za

Planned URL: https://petrolprice.co.za/about/

Page type: Trust / Brand Page   Template group: Brand / Trust   Search intent: Branded / Trust

Recommended word count: 700-1,300

1. Page Purpose

Build trust for branded users, journalists, businesses and repeat visitors. Keep claims factual and source-led. It should serve the Branded / Trust intent, answer the user’s main question quickly and guide them to the most relevant next page.

2. Target Reader

Users, partners and commercial visitors who need to understand PetrolPrice.co.za, its data boundaries, contact route or publishing policies.

3. Primary Keyword

about PetrolPrice.co.za

4. Secondary Keywords / Supporting Terms

  • PetrolPrice source
  • petrol price website
  • South African fuel price information

5. Recommended H1

About PetrolPrice.co.za

6. Recommended Meta Title

About PetrolPrice.co.za | South African Fuel-Price Information

7. Recommended Meta Description

Learn what PetrolPrice.co.za covers, how fuel-price information is organised, and where to find current prices, calculators and data sources.

8. Suggested Page Structure

H1

About PetrolPrice.co.za

H2 Outline

  • What PetrolPrice.co.za helps users do
  • Where fuel-price data comes from
  • How current, forecast and historical pages differ
  • Who the site is for
  • Key fuel-price tools

Useful H3 Topics

  • Motorists
  • commuters
  • fleet users
  • media and researchers
  • developers and data users

Required Sections from Template Rules

  • Brand promise
  • what users can do
  • key utility links
  • source/methodology notes
  • trust FAQs if useful
  • related page navigation.

9. Section-by-Section Writing Guidance

1. What PetrolPrice.co.za helps users do

  • Put the answer first. Use a current-price placeholder until the official figure has been verified, then add the effective date and units in c/l or R/l.
  • Clarify whether the context is inland, coastal, national, province-specific or fuel-grade-specific.
  • Avoid presenting a forecast, estimate or old table as the latest official price.

2. Where fuel-price data comes from

  • Put the answer first. Use a current-price placeholder until the official figure has been verified, then add the effective date and units in c/l or R/l.
  • Clarify whether the context is inland, coastal, national, province-specific or fuel-grade-specific.
  • Avoid presenting a forecast, estimate or old table as the latest official price.

3. How current, forecast and historical pages differ

  • Put the answer first. Use a current-price placeholder until the official figure has been verified, then add the effective date and units in c/l or R/l.
  • Clarify whether the context is inland, coastal, national, province-specific or fuel-grade-specific.
  • Avoid presenting a forecast, estimate or old table as the latest official price.

4. Who the site is for

  • Keep the section tightly focused on about PetrolPrice.co.za and the intent of this exact URL.
  • Use South African examples, plain language and clear distinctions between official prices, forecasts, estimates and general guidance.
  • Avoid drifting into a separate canonical topic; link to the relevant planned page instead.

5. Key fuel-price tools

  • Put the answer first. Use a current-price placeholder until the official figure has been verified, then add the effective date and units in c/l or R/l.
  • Clarify whether the context is inland, coastal, national, province-specific or fuel-grade-specific.
  • Avoid presenting a forecast, estimate or old table as the latest official price.

How to Use H3s

Use the H3 topics to break up long explanations, comparisons and examples. Keep each H3 tightly connected to the H2 above it and avoid adding unrelated keyword sections.

10. Internal Link Suggestions

Use only planned PetrolPrice.co.za URLs from this import. Add links where they help the reader move to a closely related price page, calculator, forecast, data/API page, explainer or commercial conversion page.

11. Conversion / User Action Guidance

Learn how the site uses official sources and move to current prices or data tools.

Encourage the reader to check the relevant current-price page, compare related fuel types or use a calculator to make the information actionable.

12. FAQ Suggestions

What should this page answer about about PetrolPrice.co.za?

Answer the main query in the opening section and give the user the fastest route to the relevant price, guide or tool.

What sources should be checked before publishing?

Use the official South African fuel-price source hierarchy and record the effective date where prices are mentioned.

Which related pages should be linked?

Link to only planned URLs that help the user move to price, calculator, forecast, history or data/API pages.

What should be avoided?

Avoid unverified live prices, duplicate keyword targeting and claims that belong on another canonical page.

13. Content Notes

  • Current-price caution: verify official monthly figures before inserting live price values and state the effective date.
  • Source hierarchy: use DMPR for official price schedules and monthly adjustments; use CEF for daily BFP indicators; use Gov.za statements for confirmed announcements.
  • Build trust for branded users, journalists, businesses and repeat visitors. Keep claims factual and source-led
  • Build trust for branded users, journalists, businesses and repeat visitors. Keep claims factual and source-led | FAQPage is no longer a blanket default; add it only if a visible FAQ block is implemented and schema eligibility is confirmed.
  • Do not create multiple thin brand pages. Keep branded demand consolidated around the homepage and about/trust page.
  • Canonical consolidation: this URL is the planned canonical page for “about PetrolPrice.co.za / PetrolPrice trust searches”. Build one trust/about page and link it from source notes, homepage and data/API pages. Supports branded trust and source confidence without diluting commercial current-price intent.

Schema guidance: AboutPage; WebPage; BreadcrumbList. FAQPage schema should only be added if a visible FAQ block is implemented and schema eligibility is confirmed.

Publishing/update trigger: Build now.

Final QA: confirm effective dates, units in c/l or R/l, inland/coastal labels, grade labels, forecast wording, canonical URL, internal links and anti-duplication scope before publishing.