Who Actually Owns Your Garage Door Website? A 20-Minute Audit

Somewhere in your shop’s history, somebody registered a domain, picked a host, and built a website. Maybe it was you, on a Saturday afternoon with a credit card and a bad feeling. Maybe it was a nephew, a freelancer off a Facebook group, or an agency that called cold with a good pitch. A few years pass, the person who set it up moves on, and now you’re not entirely sure who has the keys.

This is a 20-minute audit, not a project. You’re going to run five lookups, write down five answers, and know exactly what you own, what you’re renting, and what a stranger could take away from you tomorrow if they decided to. We sell garage door websites here at Garage Door Websites, so we’re not a neutral outsider writing about this industry. But this particular article doesn’t sell anything. It’s close to the same checklist we run before we’ll even quote a new build, because starting a project on top of an ownership mess is how things go sideways two months in.

Five things, and owning four of them still leaves you stuck

A website is not one thing you own or don’t. It’s five separate things, and each one can belong to a different person.

1. The domain. The actual name, like yourshopname.com. Owned by whoever is listed as the registrant of record, not whoever built the site.
2. The DNS. The settings that point your domain at your website, your email, and anything else. Sometimes managed at the registrar, sometimes moved to a separate service like Cloudflare.
3. The hosting or platform account. Where the site’s files actually live, whether that’s a WordPress host, Wix, Squarespace, or an agency platform like Duda.
4. The site itself, the files or CMS content. The pages, the images, the code. This is what “portable” or “not portable” refers to.
5. Your Google Business Profile. Separate from all of the above, tied to whichever Google account created or verified it.

Here’s the part that trips people up. You can own the domain, control the DNS, and hold your own Google Business Profile, and still be completely stuck, because the fourth item, the actual site files, sits in an account you’ve never logged into. Four out of five feels like ownership. It isn’t. The one you’re missing is usually the one that matters most when you want to leave.

What a domain registrar actually costs you

The domain is the item people check first and understand least. Three registrars come up constantly in this conversation, and they behave very differently on renewal.

Registrar	Renewal pricing pattern	Best for	Where it gets hard
GoDaddy	Promotional first-year pricing, sometimes under a dollar, jumping to roughly the low twenties per year at renewal (check current pricing at godaddy.com, checked 2026-08-28)	Owners who already have hosting or email through GoDaddy and want one bill	Renewal-price jump, and checkout upsells like privacy protection and SSL bundled in by default
Namecheap	Smaller first-year-to-renewal gap than GoDaddy, with .com renewal running around $18 to $19 a year and free WHOIS privacy included (namecheap.com, checked 2026-08-28)	Owners who want privacy included without paying extra for it	Support runs through tickets, not a phone line, so a stuck transfer can mean waiting on email
Cloudflare Registrar	No markup over what ICANN and the registry itself charge, roughly $9 to $10 a year for a .com, on renewal or otherwise (cloudflare.com/products/registrar, checked 2026-08-28)	Owners who already understand DNS and nameservers	Not typically a first-registration option. It’s best used as a landing spot after you transfer a domain away from a pricier registrar, and the dashboard assumes some technical comfort

None of these numbers are locked in. Registrars change pricing, and promotional rates especially move around. What doesn’t change is the pattern: read the renewal price, not the sign-up price, before you decide a registrar is cheap.

The 20-minute audit: five lookups

Grab a notepad. You’re answering five questions, and the honest answer to any of them might be “I don’t know” or “I’d have to ask my web guy.” That’s a real answer. Write it down.

Lookup 1: run a WHOIS on your own domain

Go to any public WHOIS lookup tool and search your own domain name. You’ll see several fields: registrant, admin contact, and technical contact. Read the registrant field specifically. That’s the legal owner of record, the only party who can authorize a transfer, release a transfer lock, or retrieve the authorization code a new registrar needs (GoDaddy’s own transfer instructions walk through exactly what that code does and who can pull it, checked 2026-08-28).

If WHOIS privacy is turned on, you’ll see a privacy service’s name instead of a person’s. That’s normal and doesn’t tell you anything bad on its own. What matters is whether the account behind that privacy shield is yours.

Lookup 2: can you log into the registrar yourself, right now

Not “could you find out.” Can you, today, without texting anyone, open a browser and log into the account where your domain lives and see it sitting there. If the honest answer is “I’d have to ask my web guy for the login,” write that down. That’s the gap between having a website and owning one.

Lookup 3: whose name and card is on the hosting or platform account

This is where a lot of shop owners get surprised. Whose name is on the hosting bill? Whose credit card gets charged every month? And when you log in, do you land in an account-level dashboard where you could cancel, export, or hand off the whole thing, or an editor-level login that only lets you change text and photos on pages someone else built?

An editor login is genuinely useful day to day. It just doesn’t answer the ownership question, because the account holder can revoke it, change the plan, or shut the whole thing down without asking you first.

Lookup 4: can the site itself actually move

This is the honest portability question, and the answer depends entirely on what platform you’re on. Self-hosted WordPress has a built-in export tool that pulls your content into a portable file (WordPress.org documents the export screen directly, checked 2026-08-28). Wix, Squarespace, Framer, and Duda do not offer anything comparable. What you built stays on their platform, full stop. Webflow sits in between: it offers a code export on some paid plans, but the export is raw code, not a finished, editable site, so it still takes a developer to turn it into something usable elsewhere (webflow.com/pricing lists which tiers include export, checked 2026-08-28).

None of this makes the closed platforms bad choices. Plenty of shops are perfectly happy on Wix or Squarespace and never intend to leave. It just means “portable” and “not portable” are two different products wearing similar-looking website builders, and you should know which one you bought.

If your current site came bundled free with a field-service tool like Housecall Pro or ServiceTitan, that’s its own flavor of this problem, and we’ve written about it separately in our breakdown of the free-website tradeoff.

Lookup 5: your Google Business Profile

Go to business.google.com and search for your business. If Google shows a message along the lines of “someone else may manage this Business Profile,” that’s your answer: somebody else, likely a former web company, still holds the keys to your listing, your reviews, and your hours.

You can select Request Access and fill out the form. Google gives the current manager a window, commonly cited as three to seven days, to respond before an appeal path typically opens up (Google’s own help documentation on requesting access walks through the flow, checked 2026-08-28, though the exact response window has shifted before and is worth re-checking at the time you actually run this). There’s no instant override button. It’s a request, not a reset.

This is also exactly the kind of setup work that belongs to our sister brand, not to us. Garage Door Websites builds and sells websites. Garage Door Lead Engine, our sister company, builds the lead-handling side of the business, and they’ve published a full walkthrough of setting up a Google Business Profile correctly for a service-area business, worth reading once you’ve reclaimed access: Google Business Profile setup for service-area businesses. We also have our own shorter piece on the setup basics, Google Business Profile setup for garage door companies.

The hard one: Duda and the agency-account problem

Every article in this series covers one product or platform that’s genuinely difficult, and this time it’s Duda.

Duda is a website builder, but it’s sold and used differently than Wix or Squarespace. It’s popular with agencies and web professionals who build and manage many client sites at once, and Duda’s own pricing page reflects that: alongside individual plans, there’s an Agency tier and a White Label tier built specifically for running a stack of client sites from one login (duda.co/pricing, checked 2026-08-28).

Here’s why that matters to you. If an agency built your site on Duda, it is entirely normal industry practice for your site to live inside that agency’s single master account, alongside dozens of other clients’ sites, rather than in an account of your own. You might have a perfectly functional editor login. The site might look and feel like it’s yours. But account-level control, the ability to export, cancel, or hand the whole thing to someone else, can sit entirely with the agency.

To be precise about what we know and don’t: this is a description of how Duda is commonly sold and used by agencies, based on the platform’s own published account structure. We found no official Duda statement saying agencies are required to run client sites this way, and plenty of freelancers and small agencies do set up an individual account per client instead. The only way to know which setup you’re in is to ask directly: “Is my site in my own Duda account, or inside your agency account?” If it’s the latter, that’s Lookup 3 all over again, and it’s worth resolving before you plan around this site being permanently yours.

What your five answers actually mean

Once you’ve run all five lookups, you’ll land in roughly one of three places.

You own everything. Domain registrant, registrar login, hosting account, and Google Business Profile all check out in your name, and you can log into each one yourself. Nothing to fix. File this audit away and check again in a year or whenever you change vendors.

You own the domain but you’re renting the site. Common, and not a crisis. This is most shops on Wix, Squarespace, or an agency platform where the domain is registered correctly in your name but the site itself lives in someone else’s account. The fix here is a conversation, not a fight: ask for account-level access, or plan your next build with portability as a requirement. If that next build is on your mind anyway, our breakdown of what a garage door website actually costs from a freelancer versus an agency is worth reading before you sign anything new.

You own close to nothing. The domain registrant is your old web company, not you, and the hosting account is theirs too. This is where it’s worth being precise about what kind of problem you actually have, because two situations that feel identical from the outside are not the same thing to fix.

A transfer-locked domain is a technical, temporary problem. ICANN policy locks a domain against moving to a new registrar for 60 days after the registrant name, organization, or email changes, unless you opt out of the lock at the exact moment you approve that change (DNSimple’s plain-language explanation of the ICANN rule walks through this, checked 2026-08-28). Annoying, but it resolves on its own on a known timeline, and it never blocks you from repointing DNS or hosting in the meantime.

A domain registered in your old agency’s own name, where you were never the registrant at all, is a negotiation, and sometimes a legal one. There’s no lock to wait out, because there was never anything registered to you to begin with. That conversation goes better when you can point to something concrete, like invoices showing you paid for the domain even though your name isn’t on it.

What usually goes wrong

The single most common mistake is treating an editor login as proof of ownership, because it looks and feels like the real thing until the day you try to leave. The second most common mistake is discovering the domain was never registered to the business at all, but to an individual person, sometimes an employee who left the company years ago and isn’t answering calls anymore.

The third is assuming a closed platform is portable because “it’s just a website.” It isn’t. If you built on Wix, Squarespace, Framer, or Duda without checking the export situation up front, the honest cost of leaving isn’t a login problem, it’s a rebuild.

The fourth, and this one is easy to miss, is confusing your website vendor with your customer data. Your website and your CRM or customer list are two different systems with two different ownership questions. If you’re also untangling a spreadsheet or an old system into a real CRM as part of cleaning this up, Garage Door Lead Engine, our sister brand, has a guide specifically on importing a customer list into a CRM without creating duplicates, which is their territory, not ours.

How to tell you got it right

You’ll know this audit actually worked when you can answer five questions without opening a single email thread: who is the domain registrant, can you log into that registrar today, whose name is on the hosting account, can the site’s content be exported if you needed it to be, and does your Google Business Profile show you as the manager. Five yeses means you’re done. Anything less than five just tells you exactly where to start.

If the answer involves asking your current web company for access, keep it short and factual. Something close to this works, in an email:

“Hi [name], doing some housekeeping on our vendor accounts this quarter. Can you confirm I have account-level access, not just editor access, to our domain registrar and our hosting or site platform account? If I’m not already the account owner, can we get that switched over? Not planning any changes, just want everything in our name.”

Most reasonable web companies will do this without friction. A refusal, or a long silence, is information too.