When the site you inherited is the problem

A lot of the work that lands on our desk doesn’t start with a blank page. It starts with a sigh.

Someone left. A freelancer stopped answering. An agency handed off a half-finished theme and a folder of passwords that don’t work. You’re the one still answering the phone when a customer says the contact form “just spins,” or when Google somehow still shows last year’s holiday hours. The homepage looks fine from across the room. Up close, it’s a museum of good intentions — and a daily tax on your patience.

That’s not a failure on your part. It’s a common place to be. And it’s fixable — usually without throwing everything away on day one, and without pretending a three-hour “quick fix” will undo years of neglect.

This is how we actually approach inherited sites at Sciocore: what we ask for, what we look at, when we repair versus rebuild, and how we leave you with something you own — not another mystery box.

How people end up here

There’s a pattern. A cousin built the first site in 2014. Then a marketing company “refreshed” it with a page builder. Then a developer added a store plugin that never quite worked on phones. Then the person who knew the hosting password moved to Colorado. Nobody wrote anything down because everyone assumed someone else would remember.

Or the nicer version: you bought a business, and the website came with the keys — sort of. The seller forwarded one email with three logins. Two of them bounce. The third opens a dashboard you’ve never seen, filled with red update notices and a theme named after a city you’ve never visited.

Or the expensive version: you paid for a custom project that never finished. The files exist. The design files don’t. The contract said “source code included,” but what you received is a zip with half a build and a README that says “TODO.”

We don’t need the drama for its own sake. We need enough history to know where the landmines are. If you can tell us who touched it last and roughly when, that alone saves days.

Before “redesign,” we stop guessing

The word redesign gets thrown around like a cure-all. Sometimes it’s right. Often it’s premature. Before anyone picks colors, we need access and a clear picture of what you’ve got.

That means, as much as you can gather:

• Domain registrar login — where the name is actually registered, not where you think it is
• Hosting login — cPanel, VPS panel, managed WordPress host, whatever’s actually serving the files
• Email — because mail and the website often share DNS, and breaking one while fixing the other is a classic disaster
• CMS admin, if there is one — WordPress, custom admin, store dashboard
• Analytics, Search Console, tag managers — if you use them
• Third-party tools tied to the site — booking, chat, payments, mailing list, review widgets, scheduling
• Any design files, brand guidelines, or old export zips sitting in someone’s Drive

If a piece is missing, we say so early. Half-rescues fail because nobody owns the keys. We’ve watched projects stall for weeks over a domain locked to an old employee’s personal email. That’s not a technical problem. It’s an ownership problem — and it has to be solved before the fun work starts.

Bring what you have. A messy spreadsheet beats a perfect story. Screenshots of error messages help. Even “I can forward the renewal emails” is a useful start.

What we look at first (the visitor’s path)

Then we look at the site the way a customer does — not the way a developer brags.

Phone first, because that’s where most people land. Are the buttons big enough for a thumb? Does the menu trap you? Does the phone number click to call, or is it a fancy image of a number? Does the form ask for seventeen fields before someone can say “please call me back”?

Desktop still matters for some industries — offices, B2B, people comparing you to three competitors with tabs open. But if the phone experience is hostile, you’re paying for traffic that leaves before it trusts you.

We check the basics that quietly kill leads:

• Broken links and 404s on important pages
• Forms that submit into the void — or into a spam folder nobody checks
• SSL warnings, mixed content, expired certificates
• Hours, addresses, and service areas that are wrong
• Pages that still mention a closed location, a retired product, or a person who doesn’t work there
• Slow loads — especially image-heavy galleries that never got resized
• Popups that attack you before you’ve read a sentence

None of that requires a philosophy. It’s respect for the person who found you and gave you thirty seconds.

Then we look under the hood

Under the hood is where inherited sites get honest.

Outdated plugins and abandoned builders. Themes that haven’t been updated because an update “might break the homepage.” Custom code taped on with no comments. Databases bloated with years of spam comments and unused revisions. Staging sites pointing at production databases. Backup plugins that say “success” but write to a folder that’s full.

We also look for security smell: leftover admin accounts named “temp,” file managers left open, old PHP versions, plugins with known issues that never got replaced. We’re not trying to scare you. We’re trying to keep you from learning about a hack from a customer screenshot.

You don’t need to understand every line. You need a short report in plain language: what’s urgent, what’s cosmetic, and what’s a money pit if you keep patching it forever.

Not every mess needs a full rebuild

Sometimes the honest answer is boring — and boring is a gift.

Update what’s outdated. Fix the form. Tighten security. Clean the copy. Leave the bones alone. If the site mostly works and customers can still find you, a careful tune-up can buy you calm without a six-month project. We’ve done that kind of work for people who were sure they needed “everything new” until we showed them the real list: three broken things and a lot of visual noise.

Sometimes the bones are the problem.

Themes fighting your real process. A page builder so tangled that changing a phone number takes an hour and breaks the footer. A store checkout that drops people on mobile. A booking flow that requires a PDF download. A homepage that looks like five different committees won five different arguments.

In those cases, patching costs more over a year than building something that matches how you actually work. We’d rather tell you that up front than sell you a “refresh” that still rests on a rotten foundation. There’s no prize for loyalty to a bad theme.

How we decide: repair, rebuild, or stage the move

There’s no single script, but the decision usually comes down to a few practical questions.

Can we make the urgent customer-facing problems go away without fighting the platform every week? If yes, repair first. Stabilize. Then decide if a rebuild is worth it later.

Is the current system actively blocking growth? New services you can’t add. A store you can’t trust. A brand that looks ten years older than the business. If yes, rebuild — but with a plan, not a panic.

Is downtime unacceptable? Then we stage: new site in the background, content migrated carefully, redirects mapped, launch when ready. You keep the old site until the new one is solid. Flashy “big reveal” launches are for people who enjoy adrenaline. Most businesses prefer Tuesday morning with a checklist.

Budget shapes the path. If money is tight, we start where it hurts customers first. Fancy can wait. Trust can’t. We’ll say what can wait without pretending the wait is free forever — deferred work is still work, just scheduled.

What a rescue usually looks like with us

Every project has its own weather, but the path is familiar.

1. Ownership and backups. We get the keys sorted so you’re not one forgotten password away from going dark. We confirm backups exist and that they restore — files and databases — not just that a plugin drew a green checkmark once in 2022.

2. Stabilize what’s broken for customers right now. Forms, hours, phone numbers, SSL, obvious errors, spam floods, pages that embarrass you. This is the “stop the bleeding” phase. It can be surprisingly emotional for owners who’ve been living with the embarrassment for years. That’s normal. Relief is part of the job.

3. Decide the destination together. Repair, rebuild, or staged move. We write it down in language you can show a partner or a bookkeeper. Scope creep loves vagueness. Clarity is kindness.

4. Protect what already works. Your brand, your content worth keeping, your photos that aren’t stock nonsense, your SEO strength where we can keep it. Redirects matter more than people think. Changing URLs without a plan is how ranking quietly evaporates while everyone argues about button colors.

5. Leave you with a site someone else could maintain. Logins that work. Notes you can read. No treasure map. If you ever leave us — and you should be free to — you take that clarity with you. Holding a client hostage with mystery accounts isn’t how we work. We’ve been in this trade too long to think lock-in is clever.

Content: keep the real voice, lose the museum pieces

Inherited sites often have two kinds of content: the stuff that’s still true, and the stuff that was true for a different version of the business.

We don’t throw away your history for the sake of looking “modern.” We do ask hard questions. Do you still offer that service? Is that pricing still right? Are those testimonials still people you’d call? Does the About page sound like you, or like a template paragraph about “synergy”?

A new site should sound like your business. Not like every other contractor or clinic or shop within twenty miles. If you’ve got a way of talking to customers — warm, blunt, funny, careful — we keep that. We’re not here to sand you down into corporate oatmeal.

Photos matter more than people budget for. Blurry phone shots of a real job often beat polished stock of strangers shaking hands. We’ll help you choose. Sometimes the right move is a short shoot. Sometimes it’s editing what you already have so it doesn’t look accidental.

SEO without the superstition

People inherit two superstitions about SEO: that it’s magic, or that it’s dead. Neither is useful.

What we care about in a rescue: clean titles and descriptions, pages Google can crawl, a structure that matches how people search for you, redirects when URLs change, and content that answers real questions — hours, service area, what you actually do. Local businesses especially get hurt by wrong NAP info (name, address, phone) scattered across old pages and directories.

We don’t promise overnight ranking miracles. We do promise not to trash what you’ve earned while “improving” things. If you’ve got years of links pointing at a URL, we treat that URL with respect.

The awkward conversations we won’t dodge

Sometimes the previous vendor is still in the picture — billing monthly for “maintenance” that was never defined. Sometimes a family member built the site and feelings are involved. Sometimes the owner wants a rebuild and the office manager wants to keep everything familiar because change is scary.

We’ll be direct without being cruel. If a retainer isn’t doing anything, we’ll say so. If a relative’s design is the reason the form doesn’t work, we’ll separate love from infrastructure. Family can still love the logo. The logo doesn’t get a vote on PHP versions.

We’re also honest about our limits. If what you need is a huge enterprise stack with a dedicated team of twelve, we’ll tell you. Sciocore is built for people who want to work directly with someone who can see the whole picture — design, code, hosting, multimedia — and who will still answer when the site hiccups at an inconvenient hour. Forty-plus years in this work taught us that availability beats theater.

Budget: what “fits” actually means

We say we work with real budgets because we mean it. That doesn’t mean everything is cheap. It means we won’t design a project that requires a second mortgage when a staged plan would get you 80% of the relief this quarter.

A typical conversation sounds like this: here’s the urgent list, here’s the rebuild list, here’s what we can do now, here’s what waits until fall, here’s what hosting should cost so you’re not surprised. You get to choose with your eyes open.

If someone offers you a rock-bottom rebuild with “unlimited revisions” and no discovery, be careful. Unlimited revisions usually means unlimited arguments. We prefer clear milestones and honest scope.

What we need from you (and what we don’t)

We need decisions when it’s decision time. We need access. We need someone who can say “yes, those hours are right” and “no, we don’t offer that anymore.” We need patience for DNS and migrations when they require waiting on the internet’s slow parts.

We don’t need a perfect brief. We don’t need you to learn our jargon first. We don’t need a slide deck. A conversation, a few examples of sites you like (and don’t), and the truth about your budget and timeline will take you farther than a twenty-page RFP copied from the internet.

If you’re in the middle of it right now

Start a folder. Dump every login email you can find into it. Forward renewal notices. Screenshot the broken pages. Write three sentences about what customers complain about most. That’s enough to begin.

If the site is actively hurting you — spam, security warnings, forms dead — say that first. Stabilization comes before aesthetics. Nobody wins a design award for a contact form that never arrives, but plenty of businesses lose work over it.

And if you’ve been embarrassed to show the site to a developer because “it’s a disaster,” don’t be. Disasters are our favorite genre. Clean greenfield projects are nice. Untangling the abandoned ones is where a lot of the craft lives — and where you feel the difference between a vendor who wants a showcase and a partner who wants your phone to stop ringing with website problems.

Where this leaves you

An inherited site doesn’t mean you failed. It means the digital side of the business accumulated history the way closets do. Someone has to open the door, sort what’s keepable, and make a plan that fits the house you actually live in.

That’s the work. Plain language. Real access. Repair when repair is enough. Rebuild when the bones are wrong. Ownership that stays with you. Support after, because launch — or re-launch — isn’t the finish line.

If the site you inherited is holding the business back, say so. Bring what you have. We’ll map a path that fits the budget you actually have, not the one a brochure assumes — and we’ll stay for the quiet work after the sigh goes away.