Florida Real Estate Website & CMS Build
Budget / Salary₹37,500–75,000
TypeFreelance project
LocationRemote
Posted12 hours ago
Real Estate Website Design, Development & SEO Project Brief
1. Project Overview
We are hiring a team to design, build, test, and launch a new real estate website from scratch. This is a complete website and publishing-system build, not an SEO audit or retainer for the existing site. The new site will use the main domain once approved for launch.
The site serves Florida homebuyers, sellers, investors, and relocating visitors. Help them find local information, understand costs and trade-offs, and request assistance. The goal is qualified inquiries and appointments—not traffic alone.
Build a scalable system for hundreds of pages on cities, neighborhoods, subdivisions, new construction, market information, and real estate questions. Pilot Lakeland before expanding. Support Google, Bing, ChatGPT Search, and Perplexity; do not guarantee rankings, recommendations, or citations.
2. Scope and Milestones
Milestone 1 — Discovery, Architecture & Design
Confirm scope, roles, dependencies, costs, and timeline.
Review the public site only for reusable assets/content, URLs, and required redirects. No work on the old site or private application.
Deliver sitemap, URL structure, data model, and mobile/desktop designs for the homepage, city hub, community guide, and long-tail answer page. Include buyer, seller, investor, and relocation navigation.
Recommend WordPress, headless CMS, or custom build; explain fit, recurring costs, portability, and nontechnical publishing.
Design references: https://mikechenrealtor.com/ | https://www.pozek.com/ | https://thenickleygroup.com/
Milestone 2 — Website & Publishing System
Build an accessible, mobile-first site with homepage, Lakeland hub, community directory, reusable templates, buyer/seller/investor and relocation sections, and tools.
Build a structured CMS connecting counties, cities, neighborhoods, subdivisions, communities, builders, guides, and calculators. Community records must support boundaries, amenities, verified and dated prices/incentives, HOA/CDD disclosures, jurisdiction, sources, original media, and next-review date/owner. Explain how shared data updates across pages.
Create an owner-to-editor workflow for notes, photos, videos, and local insights. Researchers/editors create sourced drafts (AI optional) for owner approval. Include draft, review, publish, update, and retire states; demonstrate adding/updating a community without code.
Use reusable city, community, and question templates. Generate metadata, navigation, and sitemap entries from records; retain title, slug, canonical, redirect, and indexing controls. Consolidate overlapping search intent.
Provide unique public URLs, key content in initial HTML, correct status codes/canonicals, internal links, version-controlled robots.txt/sitemap, metadata, and matching structured data. Block drafts, staging, accounts, and private data. Document crawler settings for search discovery vs. model training.
Include one lead-to-CRM flow and one calculator path in the launch quote. Price a basic ownership-cost calculator, approved tool, or external link, including maintenance/testing. Content and results must work without a form.
Milestone 3 — Lakeland Pilot & Launch
Research 100 Lakeland long-tail opportunities and deliver 10 completed, owner-approved launch pages. The 100 are a research backlog, not a publication target.
Provide an editable keyword map with query/variants, buyer decision, location, intent, evidence and date, proposed URL, local sources required, and priority. Mark unknown search volume as unknown.
Propose a launch mix covering all core templates. Suggested mix: one Lakeland hub, three community/new-construction guides, and six buyer/relocation answers. Potential topics: FHA cash to close, monthly affordability, new build vs. resale, post-purchase property-tax reassessment, HOA/CDD costs, and down-payment assistance. Keep seller and short-/long-term investor topics in the roadmap.
Include a statewide property-tax and relocation content plan. Do not present proposed tax changes as enacted law.
Answer pages need a direct answer, local example/decision aid, author or reviewer, dated sources, and relevant links. Community pages must explain local distinctions and buyer checks. Use media only with usage rights.
On staging, show an editor adding an unpublished community and reusing it for a second city. Crawl all 10 pages and document launch checks. Publish after owner approval and submit the sitemap to Search Console. Indexing/rankings are not acceptance guarantees.
Milestone 4 — Ongoing Growth (Quoted Separately)
Quote monthly deliverables for new guides, page updates, technical fixes, and reporting. Specify what your team researches, writes, edits, and publishes versus what the owner supplies.
Include an initial local SEO plan for the existing eligible Google Business Profile: accurate details, genuine reviews, and website support. No duplicate or ineligible profiles/locations.
Propose earned local mentions, relevant outreach, and legitimate partnerships. Disclose link methods and costs. No manipulative paid links, link farms, fake reviews, or bulk directory submissions.
Define criteria for expanding beyond Lakeland based on editorial quality, indexing, search demand, lead quality, and maintenance capacity.
3. Data Quality, Editorial Standards & Integrations
Use authoritative sources such as county appraisers, planning/permitting offices, school boundaries, builder disclosures, HOA/CDD records, and approved MLS data. Record source, jurisdiction, and verification date; set refresh rules for market and regulatory data.
Follow Fair Housing and brokerage advertising/disclosure rules. Keep descriptions neutral. No steering, unsupported claims, invented facts, fake reviews, copied content, doorway pages, keyword stuffing, or unreviewed bulk AI publishing.
Label estimates vs. verified figures. Review tax, lending, insurance, and rental claims; omit or clearly qualify unverifiable information.
Quote IDX/Stellar MLS, AI chatbot, accounts, advanced calculators, listing alerts, and automated follow-up separately, with dependencies and costs. Do not assume MLS access or rights. Base site must work without add-ons.
Test forms for consent, attribution, duplicates, notifications, and delivery. Quote approved KW Command integration, including Sheets/API Nation if suitable; otherwise name a secure interim destination. Never expose personal data in analytics or URLs.
4. Reporting, Testing & Acceptance
Set up owner-controlled Search Console and GA4, plus Bing Webmaster Tools if appropriate. Dashboard public URLs, indexing, organic clicks/impressions, calculator use, inquiries, qualified leads, and consultations. Define qualified lead vs. raw submission.
Baseline AI visibility with ~20 agreed customer questions; log prompt, platform, date, brand mention, citation, and cited page. Report referral traffic separately; these are observations, not universal rankings.
Before acceptance, demonstrate the complete mobile journey: visitor opens a standalone Lakeland page, uses a relevant tool, submits a test inquiry, and correct landing-page attribution reaches the approved lead destination. Demonstrate editor draft/review/publish/update workflow and documented sitemap/linking controls.
Hand over code/repository, designs, CMS configuration/export, keyword/source records, analytics/QA documentation, and editor training. Include maintenance, backups, rollback, and post-launch defect support.
5. Ownership & Responsibilities
Owner supplies brand direction, approved media, local insights, and final approvals. Contractor handles design, development, technical SEO, and staging QA. Name owners for research, writing, review, implementation, deployment, and reporting. List existing-developer dependencies and cost/timeline impact.
Owner controls domain/DNS, hosting, repository, CMS, analytics, and deliverables. Disclose third-party licenses, subscriptions, and transfer limits. Use staging/minimum access. No production-data access, launch, DNS cutover, or current-site changes without approval.
6. What Your Proposal Must Include
Start by answering: Can your team build and launch the new website and publishing system, or do you provide SEO strategy only? We will assess the ability to build, publish, and measure a working local-search system.
Two comparable live examples: URLs, your exact role, timeframe, and anonymized evidence of indexing, traffic, and qualified leads where available. Separate your results from work by others.
Proposed architecture showing how Lakeland, a community, a new-construction guide, and a buyer question are organized and internally linked.
Publishing workflow: who finds/verifies local data, what AI assists with, what humans review, and how an editor adds another community without developer support.
Named team: developer, SEO lead, researcher/writer, and final reviewer. Identify shared, subcontracted, and owner-provided roles.
Itemized fixed-price milestones separating discovery/design, website/CMS, 10-page Lakeland pilot, integrations, and launch. State page/template counts, revisions, exclusions, dependencies, timeline, and change-order terms.
Recurring costs separated into SEO/content, support, hosting, plugins, paid data, and optional integrations. State realistic monthly output at the proposed fee.
Measurement and handoff: how completion, search/AI visibility, and asset/access transfer will be verified without vendor lock-in.
Note:Compulsory Case study - two comparable live examples including urls, role, timeframe and indexing evidence, traffic and qualified leads.
1. Project Overview
We are hiring a team to design, build, test, and launch a new real estate website from scratch. This is a complete website and publishing-system build, not an SEO audit or retainer for the existing site. The new site will use the main domain once approved for launch.
The site serves Florida homebuyers, sellers, investors, and relocating visitors. Help them find local information, understand costs and trade-offs, and request assistance. The goal is qualified inquiries and appointments—not traffic alone.
Build a scalable system for hundreds of pages on cities, neighborhoods, subdivisions, new construction, market information, and real estate questions. Pilot Lakeland before expanding. Support Google, Bing, ChatGPT Search, and Perplexity; do not guarantee rankings, recommendations, or citations.
2. Scope and Milestones
Milestone 1 — Discovery, Architecture & Design
Confirm scope, roles, dependencies, costs, and timeline.
Review the public site only for reusable assets/content, URLs, and required redirects. No work on the old site or private application.
Deliver sitemap, URL structure, data model, and mobile/desktop designs for the homepage, city hub, community guide, and long-tail answer page. Include buyer, seller, investor, and relocation navigation.
Recommend WordPress, headless CMS, or custom build; explain fit, recurring costs, portability, and nontechnical publishing.
Design references: https://mikechenrealtor.com/ | https://www.pozek.com/ | https://thenickleygroup.com/
Milestone 2 — Website & Publishing System
Build an accessible, mobile-first site with homepage, Lakeland hub, community directory, reusable templates, buyer/seller/investor and relocation sections, and tools.
Build a structured CMS connecting counties, cities, neighborhoods, subdivisions, communities, builders, guides, and calculators. Community records must support boundaries, amenities, verified and dated prices/incentives, HOA/CDD disclosures, jurisdiction, sources, original media, and next-review date/owner. Explain how shared data updates across pages.
Create an owner-to-editor workflow for notes, photos, videos, and local insights. Researchers/editors create sourced drafts (AI optional) for owner approval. Include draft, review, publish, update, and retire states; demonstrate adding/updating a community without code.
Use reusable city, community, and question templates. Generate metadata, navigation, and sitemap entries from records; retain title, slug, canonical, redirect, and indexing controls. Consolidate overlapping search intent.
Provide unique public URLs, key content in initial HTML, correct status codes/canonicals, internal links, version-controlled robots.txt/sitemap, metadata, and matching structured data. Block drafts, staging, accounts, and private data. Document crawler settings for search discovery vs. model training.
Include one lead-to-CRM flow and one calculator path in the launch quote. Price a basic ownership-cost calculator, approved tool, or external link, including maintenance/testing. Content and results must work without a form.
Milestone 3 — Lakeland Pilot & Launch
Research 100 Lakeland long-tail opportunities and deliver 10 completed, owner-approved launch pages. The 100 are a research backlog, not a publication target.
Provide an editable keyword map with query/variants, buyer decision, location, intent, evidence and date, proposed URL, local sources required, and priority. Mark unknown search volume as unknown.
Propose a launch mix covering all core templates. Suggested mix: one Lakeland hub, three community/new-construction guides, and six buyer/relocation answers. Potential topics: FHA cash to close, monthly affordability, new build vs. resale, post-purchase property-tax reassessment, HOA/CDD costs, and down-payment assistance. Keep seller and short-/long-term investor topics in the roadmap.
Include a statewide property-tax and relocation content plan. Do not present proposed tax changes as enacted law.
Answer pages need a direct answer, local example/decision aid, author or reviewer, dated sources, and relevant links. Community pages must explain local distinctions and buyer checks. Use media only with usage rights.
On staging, show an editor adding an unpublished community and reusing it for a second city. Crawl all 10 pages and document launch checks. Publish after owner approval and submit the sitemap to Search Console. Indexing/rankings are not acceptance guarantees.
Milestone 4 — Ongoing Growth (Quoted Separately)
Quote monthly deliverables for new guides, page updates, technical fixes, and reporting. Specify what your team researches, writes, edits, and publishes versus what the owner supplies.
Include an initial local SEO plan for the existing eligible Google Business Profile: accurate details, genuine reviews, and website support. No duplicate or ineligible profiles/locations.
Propose earned local mentions, relevant outreach, and legitimate partnerships. Disclose link methods and costs. No manipulative paid links, link farms, fake reviews, or bulk directory submissions.
Define criteria for expanding beyond Lakeland based on editorial quality, indexing, search demand, lead quality, and maintenance capacity.
3. Data Quality, Editorial Standards & Integrations
Use authoritative sources such as county appraisers, planning/permitting offices, school boundaries, builder disclosures, HOA/CDD records, and approved MLS data. Record source, jurisdiction, and verification date; set refresh rules for market and regulatory data.
Follow Fair Housing and brokerage advertising/disclosure rules. Keep descriptions neutral. No steering, unsupported claims, invented facts, fake reviews, copied content, doorway pages, keyword stuffing, or unreviewed bulk AI publishing.
Label estimates vs. verified figures. Review tax, lending, insurance, and rental claims; omit or clearly qualify unverifiable information.
Quote IDX/Stellar MLS, AI chatbot, accounts, advanced calculators, listing alerts, and automated follow-up separately, with dependencies and costs. Do not assume MLS access or rights. Base site must work without add-ons.
Test forms for consent, attribution, duplicates, notifications, and delivery. Quote approved KW Command integration, including Sheets/API Nation if suitable; otherwise name a secure interim destination. Never expose personal data in analytics or URLs.
4. Reporting, Testing & Acceptance
Set up owner-controlled Search Console and GA4, plus Bing Webmaster Tools if appropriate. Dashboard public URLs, indexing, organic clicks/impressions, calculator use, inquiries, qualified leads, and consultations. Define qualified lead vs. raw submission.
Baseline AI visibility with ~20 agreed customer questions; log prompt, platform, date, brand mention, citation, and cited page. Report referral traffic separately; these are observations, not universal rankings.
Before acceptance, demonstrate the complete mobile journey: visitor opens a standalone Lakeland page, uses a relevant tool, submits a test inquiry, and correct landing-page attribution reaches the approved lead destination. Demonstrate editor draft/review/publish/update workflow and documented sitemap/linking controls.
Hand over code/repository, designs, CMS configuration/export, keyword/source records, analytics/QA documentation, and editor training. Include maintenance, backups, rollback, and post-launch defect support.
5. Ownership & Responsibilities
Owner supplies brand direction, approved media, local insights, and final approvals. Contractor handles design, development, technical SEO, and staging QA. Name owners for research, writing, review, implementation, deployment, and reporting. List existing-developer dependencies and cost/timeline impact.
Owner controls domain/DNS, hosting, repository, CMS, analytics, and deliverables. Disclose third-party licenses, subscriptions, and transfer limits. Use staging/minimum access. No production-data access, launch, DNS cutover, or current-site changes without approval.
6. What Your Proposal Must Include
Start by answering: Can your team build and launch the new website and publishing system, or do you provide SEO strategy only? We will assess the ability to build, publish, and measure a working local-search system.
Two comparable live examples: URLs, your exact role, timeframe, and anonymized evidence of indexing, traffic, and qualified leads where available. Separate your results from work by others.
Proposed architecture showing how Lakeland, a community, a new-construction guide, and a buyer question are organized and internally linked.
Publishing workflow: who finds/verifies local data, what AI assists with, what humans review, and how an editor adds another community without developer support.
Named team: developer, SEO lead, researcher/writer, and final reviewer. Identify shared, subcontracted, and owner-provided roles.
Itemized fixed-price milestones separating discovery/design, website/CMS, 10-page Lakeland pilot, integrations, and launch. State page/template counts, revisions, exclusions, dependencies, timeline, and change-order terms.
Recurring costs separated into SEO/content, support, hosting, plugins, paid data, and optional integrations. State realistic monthly output at the proposed fee.
Measurement and handoff: how completion, search/AI visibility, and asset/access transfer will be verified without vendor lock-in.
Note:Compulsory Case study - two comparable live examples including urls, role, timeframe and indexing evidence, traffic and qualified leads.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.