How we create and review content
This page sets out how everything we publish gets made: who writes it, who checks it, how we use AI tools, what a number needs before it goes on a page, and what happens when we get something wrong. One rule sits underneath all of it: every public claim on this site has to be one we could evidence if you asked.
1. Why we publish this
Marketing advice is cheap to produce and expensive to follow. If we suggest you change how you spend, or how you handle the people who contact you, you should be able to see where that advice came from and who stands behind it.
There is a second reason. Anyone can now generate a confident page of marketing advice in a minute. Saying ours is different costs nothing. Publishing the rules we hold ourselves to, in enough detail that you can hold us to them, is the only version of that claim that means anything.
2. What it covers
Everything we publish under our own name: the guides on our blog, our case studies, our service and about pages, and anything we share on social media that is drawn from them.
It does not cover work we produce for a client’s own site under the client’s name — that runs through the client’s approval, not ours — or material a client supplies to us, such as a quote, which we attribute rather than verify line by line.
3. Who we write for
The person who owns or runs a small or growing business, not other marketers. That reader knows their business and has no reason to know what a crawl budget is or what changed in Google last quarter. So any industry term we use gets explained in the sentence it appears in. If you find a page of ours that breaks that rule, it is a mistake and we would like to hear about it.
4. Who writes and who reviews
MapleGrowth Digital is founded and run by Rohan T George, and he is the only author on this site. Guides draw on the team’s own strategy, engineering, and delivery work; Rohan writes them and stands behind every claim in them.
Every claim about a client, every number attached to a client’s business, and every statement about what we have done is approved by Rohan before it publishes, and he is the person who says no when a draft claims more than the evidence supports.
What every guide shows
The name of the author, the date it was published, the date it was last reviewed, a sentence stating how AI tools were used, and a link to this page. If a guide is missing those, it has not finished review.
5. How we use AI tools
We use AI tools, and we say so on every guide rather than only where you might wonder. Here is the division of labour, stated plainly:
| Stage | What an AI tool does | What the founder does |
|---|---|---|
| Choosing the topic | Gathers the questions people actually search for | Decides which ones we know enough to answer honestly |
| Drafting | Structures the piece and drafts the prose | Supplies the facts, the prices, the examples, and the judgment |
| Editing | Checks readability and flags missing sections | Verifies every source and approves every claim |
| After publishing | Flags facts that may have gone stale | Decides what to update, and when |
One rule has no exceptions: no client fact, result, quotation, price, or credential is ever generated by a tool. A tool asked for a plausible number will produce a plausible number, and one invented figure would make every true one on this site worthless. When a guide says we saw something happen in real work, the founder saw it happen.
6. What a claim needs before it publishes
- A fact about how a platform works — the platform’s own current documentation, linked, or a named and dated primary source.
- A statistic — a named, dated source you can open. It appears in the guide’s references.
- A result from a client’s business — the source system, the exact period it was measured over, and the client’s written confirmation. It is shown with the period attached.
- A statement about another company or platform — taken from that company’s own published material, not from our description of them.
- Our own prices and process — these are ours to state, and they match what we quote.
- Anything we cannot source — the sentence comes out.
7. What we will not publish
- A testimonial or a case study from a client we did not have.
- A number we cannot trace to a system and a time period.
- A page written to cover a keyword variant of a question we have already answered.
- Work a partner did, described as ours.
- A recommendation we would not give a paying client.
- A prediction about what a platform will do next, written as if it were a fact.
8. How often we review what we publish
Guidance about search, advertising platforms, and AI tools goes stale faster than almost anything else a business reads. Guides that describe how a specific platform behaves are checked every quarter. Evergreen guides are checked at least once a year. A platform change, a change in a client engagement referenced on a page, or a reader telling us something is wrong each triggers a review outside that schedule.
The “last reviewed” date on a page changes only when someone has actually re-read it. It does not change to make the page look fresh.
9. Corrections
If we get a fact wrong, we correct it, note the correction at the foot of the page, and date it. We do not quietly change a published claim and leave the page looking as if it always said the new thing. Typographical fixes are not marked; everything else is.
To report an error, email info@maplegrowthdigital.ca with the page, the sentence, and what you believe is wrong. We reply within a few business days.
10. Relationships and conflicts
We sell services connected to the channels and tools we write about, and our guidance is not conditioned on any of it. Where a guide recommends a specific tool or platform we have a commercial relationship with, the guide says so. We do not use affiliate links.
We also do not solicit reviews or testimonials from anyone with a conflict of interest — a review on this site or our profiles comes from an arm’s-length client or it does not appear.
11. Contact
MapleGrowth Digital
info@maplegrowthdigital.ca