Why did I stop renting my website?
For years we paid a website company every month. They owned the software. They owned the design. If we left, we left with nothing. The pages we spent years building stayed on their servers. That is renting. You pay forever and you never own the house.
On March 19, 2026 I made the first commit on this site. That is the day it started. By the middle of April it had more than 200 community pages. Today it has more than 800 community pages, more than 850 blog posts, live home search for every MLS we belong to, lead forms that drop straight into our CRM, and a team of AI helpers that write, check, and post for us. Nobody built it for us. We built it with AI, and it is ours.
I am not a programmer. Neither are the people on my team who work on it. We type what we want in plain English, the AI writes the code, and we check the result. That is the whole trick. This page shows you exactly how, in the order we did it.
What should you tell the AI about your business first?
Give it a short project brief, just as you would brief a new team member. Name your market, brokerage, goals and budget. Gather your logo, licensed photos, approved bio, contact details and the content you have the right to move. If you are replacing a site, say which provider you use and which pages already bring traffic.
You can leave an answer blank. The AI should help you find it before choosing tools or promising a launch date. For a team, decide who approves changes, who receives leads, how leads are assigned and who handles problems after launch. Keep these decisions in a file inside the project so a new chat or a different helper can pick up the work.
Open the copy-and-fill-in website project brief
Should you start with a simple site, WordPress or custom code?
Start with the smallest useful version: a homepage, your team or about page, buyer and seller information, contact forms and a few local guides. Add a rental path if your team handles rentals. You can build these while waiting for MLS access. Start with real business information and clearly labeled sample data on the test site.
- A simple marketing site: a good first milestone when your immediate goal is explaining your services and receiving inquiries. Live MLS search can follow.
- WordPress with a supported IDX plugin: useful if you want a familiar editor and vendor-supported search. Budget for hosting, plugin updates, backups and compatible integrations.
- A custom site with an IDX API: useful when you want more control over search, listing pages and CRM workflows. You take on more responsibility for code, data refreshes, costs and support. Our stack is an example, not a requirement.
Ask the AI to compare these choices against your budget, approved MLS providers and maintenance capacity. Before buying, confirm that the IDX works with your chosen platform and that you can export your own content. A page that looks finished is still a prototype until search and lead delivery work.
Which AI should you use, Claude or ChatGPT?
Both work. We used Claude for every page on this site, so that is what I know best. The honest answer is that either one will get you there. What matters is that it can work with your project and that you save your files, your style and your rules. Do not assume a new conversation remembers earlier decisions.
The thing you actually need is the coding tool, not the chat window. Claude’s is called Claude Code. ChatGPT’s is called Codex. Both run on your own computer and edit your real files. The chat window is great for questions. A coding tool with authorized project access can create and change the site. For a hosted builder or WordPress, the workflow may instead use its editor and supported integrations.
| What | Claude | ChatGPT |
|---|---|---|
| Monthly starting plan | $20 for Pro when billed monthly; Max starts at $100. Usage limits apply. | $20 for Plus; Pro starts at $100. Usage limits apply. |
| Coding tool | Claude Code works with your project files. This is what we used to start building. | Codex works with code locally or through supported cloud tools. Choose the setup that fits your computer. |
| Your part | Explain the goal, review the result and check facts. Give it access only to the project it needs. | The same: make the business decisions, review changes and verify the finished work. |
| Keep the project consistent | Save your brand rules, choices and remaining tasks in the project. | Use the same saved project brief and change history when continuing work. |
| When to upgrade | When your actual usage needs it. A bigger plan does not replace testing. | When your actual usage needs it. API charges and add-on credits can be separate. |
My advice: start with a small project and upgrade only when your actual usage calls for it. Check the current Claude plans and OpenAI coding plans before buying. A subscription is not unlimited usage, and a website feature that calls an AI API may have its own separate bill.
Step 2What accounts do you need before you start?
Create only the accounts your chosen platform needs, under your business’s control. Use a password manager and two-factor authentication. Give collaborators their own access. Ask the AI to explain where each credential belongs; do not paste private keys, passwords or client records into a public chat or code repository.
- Your domain name. You probably already own one. If not, buy one. About $10 to $20 a year.
- GitHub. Free. This is where your site’s files live. Think of it as the filing cabinet. Every change is saved, and you can always go back.
- Vercel. This is the host. It takes the files from GitHub and puts them on the internet. Approved changes can be deployed from GitHub. Keep a test version separate from the live site and publish after checks pass. Vercel Pro starts at $20 a month, plus applicable usage.
- Supabase. Free to start. This is the database. It holds things like saved searches, leads, and anything else your site needs to remember.
- Resend. The free transactional plan allows 3,000 emails a month with a 100-per-day cap. Verify your sending domain and monitor delivery failures; form alerts and listing emails can use that allowance quickly.
- Your MLS’s IDX approval. Ask your broker, MLS and provider which approvals and fees apply. Start early; timing varies. More on IDX in Step 6.
- Google Search Console and Google Business Profile. Free. Search Console shows you what Google sees. Business Profile is your map listing if your business is eligible. Claim or update your existing profile rather than creating a duplicate.
- A CRM. We use Follow Up Boss. Confirm your CRM’s supported integration, required subscription and lead-assignment rules before choosing a form tool. This is where your leads go.
What is the one rule that makes all of this easy?
When in doubt, ask the AI. That is it. You do not need to know what a “repo” is or what “deploy” means. If a word confuses you, ask. If a screen looks wrong, ask. If you get an error, copy the whole error and paste it in. The AI is patient, it never gets annoyed, and it will explain the same thing five times if you need it to.
The screenshot trick
This is the most useful habit you will build. Whenever you are not sure if something is right, take a screenshot of what you see on your screen and paste it into the AI. Hide client details, passwords and keys before sharing the image. Then ask one of these:
This is what I see. Is this correct?
This is what I see. Fix it.
This is what I see. What do I click next?The AI can read the picture. It will spot the missing button, the wrong color, the error message in the corner, or the setting you clicked by mistake. You do not have to describe the problem in words. Just show it.
Prompts that work
Here are example prompts you can adapt. Change the names and you are off.
Build me a homepage for a real estate agent in Henderson, Nevada.
My name is ___. My brokerage is ___. My license number is ___.
I want a big photo at the top, a home search box, three buttons
(Buy, Sell, Contact), my reviews, and my phone number in the footer.Make a community page for Green Valley Ranch. Use the same layout
as the Summerlin page. Here is the real data: [paste your numbers].
Do not make up any numbers. If you do not have a number, leave it out.Explain what you just changed and why, like I am in 5th grade.What pages does a real estate website need?
Here is the full list. You do not build them all at once. You build them in the order in Step 5. But you should know the whole picture before you start, so nothing surprises you later.
| Part | Why you need it |
|---|---|
| Homepage | Who you are, where you work, a search box, and one clear button to contact you. |
| About page | Your photo, your license number, your story, and your reviews. Google and buyers both want to see a real person. |
| Community pages | One page for every neighborhood you sell in. This is where most of our search traffic lands. |
| Blog | Answers to the questions buyers and sellers type into Google. Every post is another door into your site. |
| Home search (IDX) | Live listings from your MLS, with a page for every home. Without this, people leave to search somewhere else. |
| Buyer, seller and rental pages | Explain the services you actually offer. Route each form by the visitor’s intent so a rental inquiry is not labeled as a buyer. |
| Lead forms | Every form sends you an email and drops the lead into your CRM. Test every single one. |
| Privacy, brokerage and MLS disclosures | Have your broker review the notices, listing attribution, contact consent and content rights that apply to your business. |
| Sitemap and indexing settings | Help search engines find public pages. Keep private account pages out of search and test the rules before launch. |
What order should you build it in?
Use this sequence as a set of milestones, not a ten-day promise. MLS approval, content, integrations and review may take longer. Finish and check each stage before expanding; a working small site is a better starting point than a large unfinished one.
- First: the homepage. Use the first prompt above. Look at it. Screenshot anything you do not like and ask for changes. Keep going until you would be happy to show it to a client.
- Next: about page and legal pages. Your photo, your story, your license, your reviews. Have the AI draft applicable privacy and disclosure pages for your actual tools and practices, then have your broker or adviser review them. An accessibility statement does not replace an accessible website.
- Then: one perfect community page. Pick the neighborhood you know best. Give the AI real facts: the builder, the HOA, the schools, the parks, real prices from your MLS. Make it great. This becomes the template for every other one.
- Expand: the rest of your community pages. Tell the AI to make one page per neighborhood using the template. Give it real data for each. Ten pages is a good start. We have more than 800, and we added them over months, not days.
- Connect: home search. Connect your IDX feed. This is the hardest step, and it is the one where you will lean on the AI most. See Step 6.
- Publish useful content: the blog. Ask the AI to set up a blog where each post is a simple text file. Write your first post about the question you get asked most.
- Verify delivery: lead forms. Wire every form to send you an email and drop the lead into your CRM. Then fill out every form yourself and make sure it arrives. Every single one.
- Prepare the move: move your old site. See Step 8. Do not skip the redirects.
- Launch and improve: speed and SEO. See Steps 9 and 10. Then keep adding community pages and blog posts every week.
How do you pick an IDX, and what is it?
IDX, or Internet Data Exchange, lets participating brokers display permitted MLS listings under their MLS’s rules. It is how a buyer searches homes on your site instead of leaving to search somewhere else. Every MLS has its own IDX rules and its own approval form. Fill that form out early.
You get IDX in one of two ways. A plugin is a search tool you drop into your site. Its setup and customization depend on the provider and your platform. A data feed gives your site the raw listing data, and the AI builds your search pages and listing pages from it. It takes more work and gives you control over the pages. Search visibility depends on the actual implementation and content, not simply on buying a data feed. We use a data feed.
| Option | What it is | Cost | Pick it if |
|---|---|---|---|
| Repliers (what we use) | API: your site builds search and listing pages using licensed data. | Sample-data preview is free. Standard starts at $199/month for one MLS; additional coverage and usage can cost more. | You want a custom search and have someone responsible for integration, caching and maintenance. |
| IDX Broker | IDX search for an existing website; a hosted website is also available. | Core $60/month; Engage $99; Elite hosted site $149. Setup, MLS and user fees may apply. | You want a packaged integration. Confirm compatibility, page ownership and listing URL behavior. |
| Showcase IDX | WordPress IDX plugin. | Essentials starts at $94.95/month; Premium at $124.95. MLS and additional-user fees may apply. | You choose WordPress and want a supported search plugin. |
| iHomefinder | IDX and lead-management options. | Request a current quote for your platform, MLS coverage, users and add-ons. | You want an integrated package; compare the included features with your existing CRM. |
| Your MLS’s own feed | Ask whether your MLS offers an approved data feed directly. | Request access, licensing and support costs from your MLS. | You have the technical support to maintain a direct integration. |
How to choose
- Do you want Google to rank your listing pages? Ask for a working example and check whether listings have crawlable URLs, useful visible content and appropriate canonical tags. Some plugin implementations are indexable; an API does not guarantee indexing or rankings.
- How many MLS boards are you in? Ask how the quote changes with each MLS. We are in three, and that is the biggest line on our bill.
- Who will maintain the integration? A data feed is harder to set up. Decide who handles failures, MLS rule changes, refreshes and support. Ask about request allowances and cache listing data within your agreement so every page view does not require another paid API request.
- Ask your MLS what they charge. Some MLSs charge a data fee on top of the vendor. Some charge nothing. Ask before you sign.
Whatever you pick, every listing page must show your MLS’s required disclaimer, and listings must refresh on the schedule your MLS sets. Give the AI the applicable display rules, then check the rendered pages with your broker or provider. Confirm sold, withdrawn, rental and unavailable listings behave correctly. The NAR IDX policy is background; your own MLS agreement governs your implementation.
Why did we choose Repliers for our IDX?
We wanted live MLS data inside a website we control, with our own search experience, listing pages and lead workflow. Repliers fits that approach: its API supplies the listing data, and we build the experience around it. For our team, that flexibility matters more than receiving another finished website template.
- Our design and our listing pages. Search, property details and inquiry forms can look and work like the rest of our site. We control the page layout, useful local content, internal links and indexing settings. The feed supplies licensed data; our implementation still determines whether a page is useful and crawlable.
- Search that fits our markets. We can build filters for the locations, prices, property types and sale-versus-rental searches our clients use. Repliers documents these capabilities in its listing search API. We choose which controls to expose and test the results against the actual feed.
- Regional MLS coverage in the same website. Our site serves Southern and Northern Nevada. Our integration can work with the different regional feeds rather than maintaining an unrelated website for each market. Your own MLS access still needs approval; confirm your exact boards, fields and fees with Repliers before signing up.
- Our own CRM workflow. We connect the search experience to our forms and Follow Up Boss routing, including buyer and rental intent. That connection is part of the website we built around Repliers; it is not a promise that an API subscription automatically builds or configures your CRM.
- A practical starting point for building with AI. Published API documentation and a sample-data preview give us a way to describe what we want, build it and check it. An AI coding assistant can use those references while working on the integration. You still need to verify the code, permissions, listing accuracy and finished user experience.
That is our reason for choosing Repliers. It is a fit for a custom site, rather than a claim that every other provider is wrong for every team. If you want a WordPress plugin or a packaged site with less integration work, compare those options in the table above. An API gives you flexibility and responsibility: someone must maintain it, monitor request volume, handle outages and cache data within the MLS agreement.
Also check the plan details before copying a feature from our site. Repliers’ current plan comparison separates basic search from features such as saved searches, built-in alerts and webhooks. Some features, MLS coverage and usage require a different plan or add-on. Neither choosing Repliers nor using AI guarantees search rankings or traffic like our graph.
What do LiveBy and the seller-data add-ons help you build?
Repliers can supply more than listings. Its optional data add-ons give your site information to work from instead of asking AI to guess a neighborhood boundary, school or property fact. We already use LiveBy data in our community-data integration where coverage is available. Choose additional products for the features your team actually needs.
| Data layer | What it adds | How a team can use it |
|---|---|---|
| LiveBy | Geographic and neighborhood boundaries, school and attendance-zone information, and community demographics. | Build local guides and boundary-based searches around the area a visitor means, then add sourced community context. Confirm a specific home’s school assignment with the district. |
| Public Record Parcel Data | In covered areas, parcel boundaries, ownership and mailing records, tax and assessment details, property characteristics and sales/transfer history, including off-market properties. | Help an agent research a seller’s property and check its recorded facts before a listing consultation. A public record does not tell you that an owner intends to sell or has agreed to marketing. |
| Property estimates and comparable-sales tools | An optional estimates service, used with property history and comparable listings, can support valuation research. | Build a home-value request and an agent-reviewed market analysis. Check the home’s condition and the comparable sales; an automated estimate is not an appraisal or a promised sale price. |
LiveBy is the neighborhood and community layer; the public-record product is the separate property and ownership layer. Repliers announced general availability of its Public Record Parcel Data add-on on September 22, 2026. That announcement describes a vendor capability, not a claim that we have activated it on this site or verified every county’s coverage.
For budgeting, Repliers’ LiveBy announcement lists $199/month per MLS, separate from the base subscription, with reduced pricing for additional MLSs. Ask for a current quote covering each add-on and board. Test sample addresses in your own market before committing.
The accuracy benefit is having traceable data and a repeatable check. It is not a guarantee that every field is current or that one provider is always the most accurate. Show the source and date, check important property facts against county records, and confirm attendance zones with the school district. Public records and demographic releases can lag; boundaries can differ from local usage. Have your broker review which information belongs on a public page.
Why are community pages and blog posts the most important part?
Here is how people actually find an agent online. They do not type your name. They type a question. “Is Summerlin a good place to live?” “What are HOA fees in Inspirada?” “Best neighborhoods in Henderson for families.” Every one of those questions is a door. If you have a page that answers it, they walk through your door. If you do not, they walk through somebody else’s.
That is why we have more than 800 community pages and more than 850 blog posts. Most of the traffic on this site lands on one of those pages, not the homepage. Your homepage is your front door. Your community pages and blog posts are the hundreds of side doors, and that is where the people come in.
Community pages
One page for every neighborhood, master plan, and condo tower you want to sell in. Each one should have real prices from your MLS, the HOA, the schools, what is nearby, a map, and a live list of homes for sale there. Start with ten. Add one a week. The AI writes them in minutes once you give it the facts.
Blog posts
Every question a client has asked you this month is a blog post. Closing costs. Property taxes. How earnest money works. Which side of town has the best schools. Write the answer, put real numbers in it, and say where the numbers came from. The AI can draft the post in a few minutes. Your job is to make sure it is true and that it sounds like you.
How do you make sure leads reach the right person?
Write down the expected result before testing. A buyer inquiry, seller valuation and rental tour request should have distinct labels. Include the page and property, the original acquisition source, the assigned agent and the visitor’s message. Record the consent actually given. When an existing client returns, preserve the original source and owner unless an authorized person makes a deliberate correction.
- Use test contacts you control. Mark them clearly and keep them out of real customer texts and nurture sequences.
- Test the whole route. Submit from a phone and a desktop. Open the CRM record, confirm its source and agent, and check the actual email notification.
- Test intent and duplicates. Try buyer, seller, rental, agent-page and returning-client cases. A rental should not become a buyer because a form has a default label.
- Test failures. On the test site, simulate an unavailable CRM or email service. Save the inquiry for a safe retry, prevent duplicate records and notify the person responsible.
- Respect contact preferences. Have your broker review the consent wording and your email/text workflow. Verify that opt-outs stop the relevant automated messages.
A thank-you screen is only the start of the check. Keep a simple record of which form was tested, when, and what arrived. For a team, make sure an unassigned lead or an agent who has left cannot become a dead end.
How do you move your old site carefully?
Keep your old site working while you prepare. Export the content you own, take backups and record the current domain settings, including the records that run your email. Protect the test site with access controls; an unfamiliar test address is not automatically private.
- Inventory the old pages. Use your sitemap, content export, analytics and important inbound links. Keep useful addresses when possible.
- Map changed URLs. Send an old page to its relevant replacement with a permanent 301 or 308 redirect. Avoid sending every removed page to the homepage.
- Check the new pages. Verify links, canonical addresses, indexing settings and the sitemap. Remove launch-blocking test settings only from pages intended to be public.
- Plan the switch and recovery. Preserve email DNS records, verify HTTPS and document how to restore the previous site. A domain/subdomain change may also need Search Console’s Change of Address tool.
- Monitor after launch. Check traffic, crawl errors and lead delivery. Keep redirects working long term; Google generally recommends at least one year.
Redirects reduce risk, but they do not guarantee unchanged rankings. Review Google’s site-move instructions with whoever handles the move. Cancel the old platform only after verifying that your content, leads, domain, email and redirects no longer depend on it.
Step 9How do you make the site fast?
A slow site can frustrate visitors. Speed is one part of the overall experience. Google has a free tool called PageSpeed Insights. You paste in your page address and it gives you a score from 0 to 100 and a list of what is slow. Here is the whole process:
- Run PageSpeed Insights on your homepage, a community page, search and a listing page, especially on mobile.
- Screenshot the results, or copy the list of problems.
- Paste it into the AI and say: “Here is my PageSpeed report. Fix the slowest things first.”
- Run it again. Check that search and forms still work after each change. A lab score is a diagnostic; use real-user data when available.
The usual fixes are the same on every site: pictures that are too big, pictures that load before they are needed, and too many outside scripts like chat widgets and trackers. The AI knows all of these. You just have to ask.
Step 10What are SEO, AEO, and GEO, in plain words?
These three letters get thrown around a lot. Here is what they mean and what to actually do about each.
SEO: showing up in Google search
Every page needs a clear title, a short description, one main heading, and real content. Link important public pages from other useful pages and include their canonical URLs in a sitemap. Ask the AI to check robots and noindex settings, then inspect the rendered result and submit the sitemap in Google Search Console. A submitted URL is not a promise of indexing.
AEO: showing up in the answer box
Google now answers many questions right at the top of the page. Make the answer easy to find: a descriptive heading, a direct explanation and supporting detail. Add FAQs when they resolve real reader questions. Structured data must match visible content; adding FAQ markup everywhere is not a shortcut to visibility.
GEO: showing up when people ask an AI
More and more people ask ChatGPT or Claude “who is a good agent in Henderson?” Make your business identity clear and publish useful local explanations with sources, dates and original experience. Google’s AI Search guidance says it does not use llms.txt or require special AI schema. Other services have their own rules. No file, heading pattern or AI tool guarantees a recommendation; measure actual search visits and qualified inquiries.
Step 11What do you do every week once it is live?
- Write one blog post. The question you got asked most this week. Real numbers, real source.
- Add one community page. The next neighborhood on your list.
- Check Google Search Console. Look for broken pages and for questions people are typing that you do not have a page for yet. Make that page next.
- Test one lead form. Fill it out yourself. Make sure the email and the CRM entry both show up.
Set a pace your team can maintain. Updating an existing guide can be more useful than adding another similar page. Review search clicks alongside inquiries, appointments and closings so traffic is not confused with business results.
What must work before you share the site?
Ask the AI to report each item as passed, failed or not yet checked, with evidence. Assign a person to approve the launch. A screenshot or a successful build alone does not prove the forms, access controls and integrations work.
- Mobile and accessibility: readable text, visible keyboard focus, labeled form fields, useful error messages, image descriptions and controls you can use without a mouse. Review the DOJ’s web accessibility guidance; an overlay or a statement is not the test.
- Real content and permissions: correct contact details, approved brokerage and MLS disclosures, accurate local facts, licensed photos and genuine reviews. Never copy this team’s identity, reviews or results into your own site.
- Search and lead delivery: working filters, accurate rental/sale labels, current listing status, correct agents and end-to-end form checks.
- Private data: another visitor cannot read a lead or another user’s saved account. Test admin permissions. Keep private credentials in server-side settings; Supabase explains which keys must stay secret.
- Migration and recovery: working redirects, HTTPS, email, sitemap and indexing settings; a saved code version and a tested way to restore the database and uploaded files.
- Ongoing ownership: name the person who receives failure and billing alerts, handles updates and can roll back a broken release.
How do you avoid silent failures after launch?
Monitor the result, not just whether a scheduled job ran. If a listing alert was due, confirm it was accepted for delivery. If a lead arrived, confirm the CRM received it. Record the last successful result, retry safely without duplicates, and alert a person when something is overdue. Check MLS and map usage against the plan’s limits so a traffic spike does not become a surprise bill.
Keep a short maintenance log with the change, the checks performed and any unresolved issue. Ask the AI to read it before making the next change. Backups, tested recovery and a named owner make the site maintainable when someone is away.
What does it cost each month?
Build your budget from the tools and usage you actually need. These are starting prices checked September 23, 2026, not our invoice, an all-in quote or maximum charges. Taxes, additional MLS access and team accounts can change the total.
| Item | Starting point | What else to budget |
|---|---|---|
| AI helper | $20/month starting plan | Higher-usage plans, credits and API usage can add to the bill. Choose based on actual usage. |
| Hosting (Vercel example) | Pro starts at $20/month | Budget for applicable seats and usage. A free hobby plan is not the business-site budget. |
| Database (Supabase example) | Free tier; Pro from $25/month | Pro includes daily database backups. Storage, compute, retention and extra projects can add costs. |
| Transactional email (Resend) | Free tier; Pro $20/month | Free: 3,000 emails/month, capped at 100/day. Pro: 50,000/month; extra volume costs more. |
| IDX / MLS | Use your chosen vendor’s quote | Include MLS coverage, setup, team seats, request limits and paid extras; see the comparison above. |
| Domain, maps and CRM | Quote separately | Include domain renewals, any paid map usage, CRM seats and integration tools. Free allowances are not a spending cap. |
| Maintenance and review | Allocate time or a support budget | Include backups, security updates, content checks and help with issues you cannot verify yourself. |
For example, $20 AI + $20 hosting + $25 database + $199 IDX = $264/month before extras. That illustration uses a single MLS and the free email allowance; it leaves out domain, CRM, maps, support, tax and usage overages. A plugin site has a different mix. Get a written quote and set usage alerts before launch.
What mistakes should you avoid?
These are the ones we made, so you do not have to.
- Letting the AI make up facts. It will. Give it real data and tell it not to invent numbers. Check every price, fee, and rating before it goes live.
- Building the new site and then trying to figure out redirects. Do the redirect list first. It is boring. It is also the thing that protects your rankings.
- Skipping the legal pages. Have your broker review the disclosures, contact-consent wording and data practices that apply. AI can help draft them, but a generic template is not approval.
- Not testing the forms. A form that looks fine and sends nothing is worse than no form. Fill out every one yourself.
- Trying to build everything in one weekend. Build the homepage. Enjoy it. Then build the next thing. Small wins keep you going.
- Not asking. Every single time we got stuck, the answer was to ask the AI one more question, usually with a screenshot. If the answer cannot be verified, pause that change and ask the relevant vendor or a qualified developer. Confident wording is not evidence.
What do the technical words mean?
- Domain
- Your website address. Keep registration and recovery access under your control.
- Hosting
- The service that makes your site available on the internet.
- Repository and commit
- A saved project and a recorded change to it. This history helps you review or undo changes.
- Preview and deployment
- A test version and the process of putting a checked version online.
- API and CRM
- An API lets systems exchange information. Your CRM is the system where your team manages contacts and follow-up.
- DNS and redirect
- DNS points your domain to services such as your website and email. A redirect sends a visitor from an old page address to a new one.
Where can you check the instructions and prices?
The vendor names and prices above link to official pages checked September 23, 2026. Verify the current terms before buying. For the work itself, start with these official resources:
- Claude Code quickstart and OpenAI’s Codex setup guide.
- Google’s migration checklist and Google’s AI Search guidance.
- NAR’s IDX overview, plus your own broker’s and MLS’s current agreement.
- DOJ web accessibility guidance and Vercel’s test and production environments.
Frequently Asked Questions
Does Repliers offer LiveBy and data for seller tools?
Why did Nevada Real Estate Group choose Repliers for IDX?
Can I just give this guide to AI and ask it to build my site?
Do I need to know how to code?
Should I use Claude or ChatGPT?
How long should I allow?
What does it cost each month?
Will redirects guarantee that I keep my rankings?
Do I need IDX before I can start?
How do I know a lead form really works?
Want to see it working before you start?
Everything on this page describes the site you are reading right now. Click around. Open a city page, a home search, a blog post, and a community page. All of it was built the way this page describes, by people who are not programmers, with an AI helper and a lot of screenshots.
If you are an agent in Nevada and you would rather plug into a site that is already built, that is what our team gets. Here is how to join. Either way, stop renting. Own it.
About Chris Nevada
Chris Nevada leads Nevada Real Estate Group, Nevada’s #1 real estate team, with 150+ agents, 9,600+ closed transactions, and 9,146+ verified five-star reviews. Licensed in Nevada (S.181401), brokered by LPT Realty. Southern Nevada: (702) 637-1759. Northern Nevada: (775) 277-2120.