Write for Us — Land Measurement & Property Guides

Pitch to gemprogrammersgp@gmail.com with a working title, a short outline and one link to something you have written. We reply to every pitch that fits the topics below.

Topics we want

The unifying thread is Indian land measurement and the practical problems it creates. The more specific and first-hand the article, the more likely we are to publish it.

• State or district-level measurement conventions, especially where local usage differs from the commonly-published figure.
• How to read a record of rights — khatauni, 7/12, jamabandi, porcha, chitha — and what its area field actually means.
• Land records digitisation in a particular state, and what has and has not changed for buyers.
• Surveying practice: how a licensed surveyor establishes area and boundary, and when it is worth commissioning one.
• Case studies of measurement disputes and how they were resolved, with identifying details removed.
• Regional units we do not yet cover — Manipur's sangam, Kerala's cent, Tamil Nadu's ground and kuzhi, Karnataka's gunta.
• Agricultural land purchase due diligence, tenancy rights and land ceiling rules by state.

What we do not accept

• Generic 'top 10 tips for buying property' articles with no measurement content.
• Anything written primarily to place a backlink. We remove commercial links, and a pitch that is obviously link-driven gets declined.
• AI-generated drafts submitted without review. We can tell, and more importantly the figures in them are usually wrong.
• Content republished from elsewhere, including your own site. It must be original and unpublished.
• Articles that state a single national bigha-to-acre figure without naming a state. That is the error this site exists to correct.

Editorial standards

1. 1,200–2,000 words. Shorter is fine if the topic is genuinely narrow; padding is not.
2. Every numeric claim needs a source — a state land revenue portal, a settlement record, a published survey manual or a named official document.
3. Every conversion figure must name the state it applies to and be labelled as a commonly-cited approximation.
4. Where a state runs competing conventions, mention them rather than picking one silently.
5. Plain English or plain Hindi. Explain a term the first time you use it.
6. No legal advice. Point readers at the record and at professionals rather than telling them what to do.

How to pitch

1. Email gemprogrammersgp@gmail.com with the subject line "Guest post pitch — [your topic]".
2. Include a working title, a three to five point outline, and one line on why you are the person to write it.
3. Attach or link one previous piece of writing. A blog post or a LinkedIn article is fine; it does not need to be published on a large site.
4. Do not send a finished draft in the first email. We would rather agree the angle first than have you write 1,800 words we cannot use.

We reply to every pitch that fits the topics above, usually within a week. If the angle works we will confirm the brief, agree a deadline and send you the house style notes.

What contributors get

• A byline with your name, a one-line bio and one link to your site or professional profile.
• Author credit in the article's structured data, so your name is attached to the piece for search engines and AI answer engines.
• Internal links from relevant existing articles, so the piece is not published into a dead end.
• Editing for clarity and house style. We will not change your argument without asking.

We do not pay for guest articles at present, and we say so up front rather than after you have written one.

Before you pitch

Read a couple of the existing guides to see the level of specificity we are after, and the about page for how we derive figures. If your article would contradict something we have published, that is interesting — say so in the pitch, and bring the source. For anything other than a pitch, use the contact page.