Our standard
Everything published here should be original, accurate, useful to a real reader and checkable. If a piece of writing does not help someone play better, build better or understand something they did not understand before, it does not need to exist.
Originality
All content is written specifically for this site. We do not spin, rewrite or paraphrase other people's articles, we do not scrape competitors, and we do not mass-produce pages to fill a content calendar.
Game descriptions are written from playing the game, not from a template. That is why the description of Donut Run talks about a sugar meter and the description of Gravity Kitchen talks about landing on the underside of a counter: those are the things that actually distinguish them.
Research and sourcing
Three rules govern how claims get into an article:
- Claims about our games are verified against our game code. When an article states a combo threshold, a power-up radius or a difficulty multiplier, that number is read out of the source file that implements it. Those files ship with the site and can be inspected in your browser.
- Claims about web technology are verified against primary documentation. The relevant specification, or MDN where it summarises the specification accurately. Not a blog post repeating a blog post.
- Claims we cannot verify do not get published. If we cannot source it, we either leave it out or state plainly that it is our judgement rather than a fact.
What we will not publish
- Invented statistics, player counts, download numbers or engagement figures.
- Fabricated studies, surveys or citations.
- Quotes from people who did not say the thing.
- Fake reviews, fake testimonials or fake ratings — including in structured data.
- Claims of worldwide popularity we have no data to support.
- Health, nutrition or dietary guidance of any kind.
- Keyword-stuffed text written for search engines rather than readers.
- Content copied, spun or closely paraphrased from another site.
On structured data
Our pages include JSON-LD describing games, articles, breadcrumbs and FAQs. It only ever describes information that is visible on the page. We do not publish aggregate rating markup, because we have no rating system and inventing one would be a lie told to a search engine.
Game testing
Every game is played to a game-over state on all four difficulty presets, on desktop and on a phone, before publication. The test confirms that controls respond, collisions register, the score and combo readouts match what happened, pause and restart work, the local high score persists, and touch controls never cover the HUD in either orientation.
It also confirms the fairness properties we claim: that difficulty ramps flatten out, that generated gaps are within the character's real jump reach, that games pause when the tab is hidden, and that nothing in the run depends on a particular frame rate.
When a game is rebalanced after publication, its "last updated" date changes and any article describing the changed behaviour is checked and updated too.
Quality control before publishing
- Draft written from playing the game or reading the source, never from a template.
- Every factual claim traced to the code or to primary documentation.
- Internal links added where they genuinely help — category, related games, related guides.
- Metadata written by hand: unique title, unique description, unique H1.
- Heading hierarchy checked for correct nesting.
- Read end to end for whether it is actually useful, and cut where it is padding.
- Sitemap regenerated and the new URL confirmed to resolve.
Editorial independence
The site carries advertising. Advertising has no influence over what we publish, how a game is described or what a guide concludes. We do not publish sponsored posts presented as editorial, we do not sell links inside guides, and we do not accept payment to feature a game.
If that ever changes, any paid placement will be labelled clearly and unmistakably as such, at the top of the page it appears on.
AI assistance
We use software tools during production, including for drafting, editing and code review. We are telling you this because you deserve to know how content is made, not because it changes our responsibility for it.
What matters is the standard applied afterwards. Nothing is published unchecked. Every factual claim about our games is verified against the game code by a person; every claim about web technology is verified against primary documentation by a person; every game is played by a person before its page goes live. A tool that produces a plausible-sounding but unverified sentence is a liability, and is treated as one.
Updates and corrections
Articles are reviewed when the thing they describe changes — a rebalanced game, a new browser behaviour, a new mechanic. Updated pieces carry a visible "updated" date, and we do not touch that date for cosmetic edits: it means the content actually changed.
Corrections are handled under the fact-checking policy. Errors are fixed promptly; substantive errors get a correction note on the article. We do not quietly delete pages that turned out to be wrong.
Report an error to editorial@playfoodarcade.xyz.
Authorship
Content is published under the byline of Alex Morgan, the site's editorial persona, whose profile page states plainly that the persona is fictional and lists exactly what it does and does not claim. We do not attribute articles to invented experts with invented credentials.
Publishing cadence
Up to two substantial articles a day when there is genuinely something worth writing about, and nothing at all when there is not. Frequency is not a goal. A site with sixty good pages beats a site with six hundred thin ones, for readers and for search engines alike.
Frequently Asked Questions
Who writes the content on Food Arcade?
All editorial content is published under the byline of Alex Morgan, the site's stated editorial persona. The author page describes plainly what that persona is and is not.
Do you accept sponsored posts?
No. We do not publish paid content presented as editorial and we do not sell links inside guides.
Do you use AI to write articles?
We use software tools during production and say so openly. Nothing is published unverified: claims about our games are checked against the game code and claims about web technology against primary documentation.
How do I report an error?
Email editorial@playfoodarcade.xyz. Verified errors are corrected, and substantive corrections are noted on the article.
How often do you publish?
Up to two substantial pieces a day, and nothing when there is nothing worth publishing. Quality is the constraint, not the calendar.