Engaging SEO-Driven Content for Real Estate Blog
Budget: €250 – €750 EUR
1. Project Context
Our portal is Indonesia's leading real estate portal, part of the Lifull Connect portfolio.
We are running an SEO-driven content push for the blog, targeting 16 articles. Each article must target a specific Indonesian-language keyword identified through Google Search Console and keyword research (this will be provided to you), with an existing landing page that will link back to.
Workflow: you will write each article in English, following the brief and keyword guidance below. Our in-house team will translate and localize the final English draft into Bahasa Indonesia, so the English version does not need to be SEO-optimized for English search - it needs to be well-structured, factually sound, and easy to translate faithfully.
Why English first: this lets us brief, review, and edit efficiently in English before localization, while keeping full control over the final Indonesian SEO copy (keyword placement, tone, and local nuance) in-house.
2. What We Need From You
- 16 articles in English, ranging roughly 1,200–2,000 words depending on topic depth (this will be provided to you).
- Each article follows the structure and search intent noted for that title (transactional vs. informational - see below).
- Original, well-researched content - no direct translation from existing Indonesian sources, no AI-generated filler, no plagiarism. We will run originality checks.
- Local property/finance context should be plausible and general (e.g. "a subsidized mortgage program", "a government-backed low-cost housing scheme") since exact Indonesian regulations, bank names, and figures will be verified and localized by our in-house team during translation. Do not invent specific statistics, interest rates, or legal figures — flag where local data belongs with a placeholder like [LOCAL DATA: current BI rate].
- Delivery as Google Docs (one doc per article), with the English working title as the doc title.
- Meta title suggestion (English, 55–60 characters) and meta description (140–155 characters) at the top of each doc, for our translators' reference.
3. Article Types & Structure
3.1. Transactional intent articles (Location Guides - buy/rent specific areas)
Readers are close to a buying or renting decision. Structure:
- Intro: why this area/city is attractive right now (2026 framing).
- Price ranges by property type (house/apartment, by size or bedroom count) — use realistic ranges, flag exact figures as [LOCAL DATA].
- Best neighborhoods/sub-areas within the city, with a one-line reason for each.
- Practical tips: what to check before buying/renting, red flags, negotiation tips.
- Short FAQ (3–5 questions) addressing common buyer/renter concerns.
- Closing CTA paragraph pointing readers to browse listings (we will localize the link).
3.2. Informational intent articles (Buyer Process & Legal, KPR & Finance)
Readers are researching before deciding. Structure:
- Intro: define the topic and why it matters to the reader.
- Step-by-step or comparison breakdown (numbered steps for processes; a clear comparison table for "vs." topics like Sharia vs. Conventional KPR, or SHM vs. HGB vs. SHSRS).
- Requirements/documents needed, where applicable.
- Common mistakes or things people overlook.
- Short FAQ (3–5 questions).
- Closing CTA paragraph.
4. Tone & Style Guide (English draft)
Even though this is an intermediate English draft, tone matters - it determines how the final Indonesian reads after translation.
- Voice: helpful, knowledgeable friend - not a salesperson, not a legal textbook. Write as if explaining the topic to a first-time buyer or renter who is a bit overwhelmed.
- Register: clear and conversational, but credible. Avoid slang and avoid overly formal/academic phrasing. Short paragraphs (2-4 sentences), short sentences where possible.
- Person: second person ("you") when addressing the reader directly; first-person plural ("we") only in the closing CTA if referring to ou .
- Structure over prose: favor headers, numbered steps, bullet lists, and short tables over long unbroken paragraphs - this also makes translation faster and more accurate.
- Confidence without overreach: be direct and practical ("Here's what to check before signing"), but do not state specific legal, tax, or financial figures as fact - use placeholders per Section 2.
- Avoid: hype language ("amazing deal", "once in a lifetime"), humor that may not translate well, idioms, and culturally specific references that don't map cleanly to Bahasa Indonesia.
- Headings: write headings as clear, literal descriptions of the section content (these guide the translator's H2/H3 structure) rather than clever or punny headlines.
5. Review & Revisions
- We will review each draft against this brief and the keyword/intent for that article before it goes into translation.
- Standard scope includes up to 2 rounds of revisions per article at no extra cost, covering structure, tone, and factual placeholders (not a full rewrite).
- Please flag any topic where you're unsure of the correct local context rather than guessing - a placeholder is always preferred over an invented fact.
Our portal is Indonesia's leading real estate portal, part of the Lifull Connect portfolio.
We are running an SEO-driven content push for the blog, targeting 16 articles. Each article must target a specific Indonesian-language keyword identified through Google Search Console and keyword research (this will be provided to you), with an existing landing page that will link back to.
Workflow: you will write each article in English, following the brief and keyword guidance below. Our in-house team will translate and localize the final English draft into Bahasa Indonesia, so the English version does not need to be SEO-optimized for English search - it needs to be well-structured, factually sound, and easy to translate faithfully.
Why English first: this lets us brief, review, and edit efficiently in English before localization, while keeping full control over the final Indonesian SEO copy (keyword placement, tone, and local nuance) in-house.
2. What We Need From You
- 16 articles in English, ranging roughly 1,200–2,000 words depending on topic depth (this will be provided to you).
- Each article follows the structure and search intent noted for that title (transactional vs. informational - see below).
- Original, well-researched content - no direct translation from existing Indonesian sources, no AI-generated filler, no plagiarism. We will run originality checks.
- Local property/finance context should be plausible and general (e.g. "a subsidized mortgage program", "a government-backed low-cost housing scheme") since exact Indonesian regulations, bank names, and figures will be verified and localized by our in-house team during translation. Do not invent specific statistics, interest rates, or legal figures — flag where local data belongs with a placeholder like [LOCAL DATA: current BI rate].
- Delivery as Google Docs (one doc per article), with the English working title as the doc title.
- Meta title suggestion (English, 55–60 characters) and meta description (140–155 characters) at the top of each doc, for our translators' reference.
3. Article Types & Structure
3.1. Transactional intent articles (Location Guides - buy/rent specific areas)
Readers are close to a buying or renting decision. Structure:
- Intro: why this area/city is attractive right now (2026 framing).
- Price ranges by property type (house/apartment, by size or bedroom count) — use realistic ranges, flag exact figures as [LOCAL DATA].
- Best neighborhoods/sub-areas within the city, with a one-line reason for each.
- Practical tips: what to check before buying/renting, red flags, negotiation tips.
- Short FAQ (3–5 questions) addressing common buyer/renter concerns.
- Closing CTA paragraph pointing readers to browse listings (we will localize the link).
3.2. Informational intent articles (Buyer Process & Legal, KPR & Finance)
Readers are researching before deciding. Structure:
- Intro: define the topic and why it matters to the reader.
- Step-by-step or comparison breakdown (numbered steps for processes; a clear comparison table for "vs." topics like Sharia vs. Conventional KPR, or SHM vs. HGB vs. SHSRS).
- Requirements/documents needed, where applicable.
- Common mistakes or things people overlook.
- Short FAQ (3–5 questions).
- Closing CTA paragraph.
4. Tone & Style Guide (English draft)
Even though this is an intermediate English draft, tone matters - it determines how the final Indonesian reads after translation.
- Voice: helpful, knowledgeable friend - not a salesperson, not a legal textbook. Write as if explaining the topic to a first-time buyer or renter who is a bit overwhelmed.
- Register: clear and conversational, but credible. Avoid slang and avoid overly formal/academic phrasing. Short paragraphs (2-4 sentences), short sentences where possible.
- Person: second person ("you") when addressing the reader directly; first-person plural ("we") only in the closing CTA if referring to ou .
- Structure over prose: favor headers, numbered steps, bullet lists, and short tables over long unbroken paragraphs - this also makes translation faster and more accurate.
- Confidence without overreach: be direct and practical ("Here's what to check before signing"), but do not state specific legal, tax, or financial figures as fact - use placeholders per Section 2.
- Avoid: hype language ("amazing deal", "once in a lifetime"), humor that may not translate well, idioms, and culturally specific references that don't map cleanly to Bahasa Indonesia.
- Headings: write headings as clear, literal descriptions of the section content (these guide the translator's H2/H3 structure) rather than clever or punny headlines.
5. Review & Revisions
- We will review each draft against this brief and the keyword/intent for that article before it goes into translation.
- Standard scope includes up to 2 rounds of revisions per article at no extra cost, covering structure, tone, and factual placeholders (not a full rewrite).
- Please flag any topic where you're unsure of the correct local context rather than guessing - a placeholder is always preferred over an invented fact.