Get Your Site Made Blog
- Why a website needs updates after it's already live
The software under a website keeps changing even when nobody touches it. Here's what core and plugin updates actually do, and why they get skipped.
- Whose job is it when something on your website breaks
A site breaks months after launch and nobody agreed in advance who's responsible. Here's how to sort out who actually owns the fix.
- Who takes care of your website after launch
Launch day feels like the finish line, but a website needs hosting, backups, updates, and someone to answer when it breaks. Here's who that's supposed to be.
- What website security monitoring actually catches
Malware scans, brute-force blocking, and breach cleanup explained in plain terms, plus where monitoring stops and a person has to step in.
- What website hosting actually is, and who's supposed to pay for it
A plain-English walkthrough of what hosting actually does, who typically holds the account, and what happens when a bill lapses.
- What to ask before you agree to a monthly website retainer
A vague three-bullet retainer contract just landed in your inbox. Here's exactly what to pin down before you sign it.
- Your web designer has gone silent - what to do now
Unanswered emails, a domain renewal coming due, and no reply in sight. Here's what to check, what to send, and when to call it abandoned.
- What actually happens in the first hour your website goes down
A timeline of the first hour after a site outage: what to check first, who to call, and how most outages actually get fixed.
- The domain and SSL renewals nobody remembers until they lapse
A not-secure warning shows up out of nowhere, or a domain quietly goes up for sale. Here's the renewal timeline behind both, and how to stay ahead of it.
- Is a website maintenance plan worth paying for
A maintenance plan bundles a few different jobs into one bill. Whether that's worth it depends on your site, your time, and what the plan actually promises.
- How you would actually know if your website went down
A monitoring tool, a customer complaint, or nothing at all. Here's what each actually gets you when your website goes down, and how to set up the first one.
- How to move your website away from a designer who is gone
You've decided to leave. Now comes the practical part: confirming access, getting the rest in writing, and moving hosting and the domain without losing them.
- How a website is supposed to grow after the launch date
A site frozen at its launch-day state is a site quietly going stale. Here's what actually needs to change over time, and who's meant to change it.
- Does your website actually have backups, and who can restore them
A backup that has never been restored is a guess, not a safety net. Here's how to check what's actually saved, where, and who can bring it back.
- Can you switch web designers partway through a project
Leaving is nearly always possible. What decides how expensive it gets is the contract's exit terms, what you already hold in your own accounts, and how usable the unfinished site actually is.
- What to ask about accessibility before you sign with a web designer
Six questions worth asking before a deposit clears, and what a reassuring-sounding answer that commits to nothing actually looks like.
- Small businesses do get sued over their websites, and the filings say so
What the UsableNet ADA Lawsuit Tracker actually counts, why there's no small-business exemption, and what a demand letter usually looks like before any filing.
- Website accessibility for a small business, without the panic or the jargon
A plain-language starting point for small business website accessibility — what it covers, what it doesn't, and which legal-adjacent pages are worth reading next.
- The terms page nobody reads still has a job to do
A terms page does quiet work even on a site with nothing to sell, and changes completely once bookings or deposits start moving through it.
- The menu that is a photograph and the price list that is a PDF
A photographed menu or an unstructured PDF is invisible to a screen reader and unreadable on a phone. Here's how to rebuild it without losing the design.
- How to tell whether an accessibility audit is worth paying for
Two audit quotes that look nothing alike usually differ in the proposal, not the price. Here's what to check before you pay for one.
- Ten minutes with a keyboard tells you more than any scanner
A hands-on sequence for checking your own site's accessibility this afternoon, with the keyboard, phone, and screen reader you already own.
- Does a small business site need a privacy policy, and who should write it
What an ordinary contact form actually collects, what a policy has to say to be true, and when a template stops being enough for your site.
- The cookie banner you copied describes somebody else's tracking
What actually sets a cookie on a plain brochure site, and how to tell whether your banner is doing its job or just covering your phone number.
- The accessibility widget in the corner of the screen, and what it does not do
What an overlay widget changes on a page, what it leaves untouched underneath, and what UsableNet's litigation data says about sites that used one anyway.
- Grey text on a white background is a habit, not a design style
Why pale type that looks fine on a designer's monitor fails outdoors, and how to check and fix contrast without any design training.
- Captions, autoplay, and the video that starts talking on its own
Who actually needs captions, why auto-generated ones still need editing, and what autoplay and background motion do to some visitors.
- The photo you found on Google is somebody's invoice waiting to happen
Free, royalty-free, and licensed images are three different things — and how a licensed photo can end up unlicensed the moment a designer moves on.
- Writing alt text for a photograph of your own shop
A practical guide to writing image descriptions that actually help — for shop photos, logos, decorative images, and galleries with hundreds of files.
- The contact form is where an accessibility problem costs you money
Why vanishing labels, vague error messages, and unfriendly captchas on a contact form quietly cost a small business real enquiries.