Rural property blog

The blog is for dated explainers that sit beside the evergreen guides. New posts are Keystatic documents in content/posts/. An editor adds a post the way they would in WordPress: title, permalink, meta description, hero, FAQs, related links, and a Markdoc body. The catch-all route publishes it at the permalink.

This is not a news wire and not a listings alert. We will not email you “hot farms” or invent a clearance rate for last week’s district auction.

Current posts

• Reading a rural contract of sale — how a farm contract differs from a house contract, and which schedules actually matter.
• Biosecurity when you buy a farm — livestock traceability, plant health and why a “walk-in walk-out” sale is also a biosecurity event.
• Native title and rural land — registers to ask a practitioner to search, without pretending a blog post is a native-title opinion.

How this relates to the guides

Evergreen pages in /guides/ are the syllabus. Blog posts are the essays you assign after the syllabus: a closer look at one document, one risk, or one official register. If a post and a guide disagree because the law moved, the official source wins and we update the updated field.

Start with the buying guide or the due diligence checklist if you landed here from a search. Use the guest-post page if you want to pitch a dated explainer rather than an advertorial.

Historic context

Earlier versions of this domain mixed Rural Press classifieds with later WordPress marketing. The blog restores an editorial layer without restoring invented testimonials. Guest URLs that still collect backlinks are kept on their old paths and labelled as guest education.

Corrections go through the contact form. Do not send identity documents.

Editorial rules for dated posts

Blog posts may date-stamp a FIRB check or point at a newly moved ATO URL. They may not invent a market report. If we cannot cite a primary source, we do not publish the number. Corrections update the Keystatic updated field.

Posts are Markdoc. Editors should add FAQs when a question is quotable, and related links back into the evergreen guides so the blog does not become an island.

Suggested next posts (not yet written)

Editors can add, through /keystatic/, explainers on rural GST going concerns, on reading a water-register extract, or on council primary-production rating versus ATO status — provided each piece cites the official desk. That is how this collection is meant to grow, the way a WordPress posts folder would.

Until those exist, the three current posts plus the guides are the syllabus. Pitch via contact.

How the blog relates to Keystatic

Open /keystatic/ while the site is running locally (npm run dev). Choose Blog posts, add a slug, set permalink to blog/your-post-name, paste Markdoc, add FAQs if a question should be schema-marked as FAQPage, and commit the .mdoc file. The catch-all route at src/app/(public)/[...slug]/page.tsx publishes anything whose permalink matches. That is the WordPress-like workflow this rebuild promised: editors do not need to ship a new React page for every article.

Do not use the blog for listings, price guides, or unnamed testimonials. Use guest posts if the piece is contributed. Use guides if the piece should stay evergreen. Use editorial policy if you are unsure.

Historic classifieds that used to feel “blog-like” on this domain were newspaper ads. They are not restored. State hubs now carry the education those URLs deserved.

What we will date-stamp

FIRB thresholds (last checked 2 January 2026 on the agricultural-land note), ATO page moves, and water-register interface changes are fair game for a dated post. District “market heat” is not, unless a primary statistical publisher is cited — and even then we will link rather than freeze a number that will be wrong next quarter.

The three current posts are enough to prove the workflow. Editors should add more through Keystatic rather than asking for a new React route. Internal links back to buying, selling, water and the state hubs are mandatory on new posts so the blog cannot drift into orphan marketing.

Reading order

New readers should not start here. Start on guides or a state hub. Come to the blog when you need a closer look at one document — the contract, the biosecurity movement, the native-title register. That is how a dated collection supports evergreen pages instead of competing with them.

Editors who want a WordPress-like cadence can publish short, sourced explainers as often as the official desks move. We would rather have four accurate posts than a weekly “market wrap” with invented clearance rates. The contact form is for corrections and pitches, never for sending contracts.

Keystatic storage is local git. There is no WordPress database to back up. A post is a file. That is a feature: pull requests review YMYL copy before it is live. Do not paste unnamed testimonials into a new post to “warm it up”. The old theme already tried that; we deleted it.