.htaccess & Redirect Fix
A single wrong line in .htaccess can take an entire site down or send visitors into an endless redirect loop. It is also one of the quickest things to fix correctly once you can read what it is actually doing.
Price confirmed after a quick look, before any work starts. If your case is more involved, you get a revised quote to approve — never a surprise invoice.
- Typical turnaround
- Same day
- Guarantee
- 14 days
- Fixed-price quote first
- Root-cause fix, not a band-aid
- 14-day correction guarantee
Symptoms I see with this.
If any of these describe what you're looking at, this is the right fix. If you're not sure, describe it and I'll point you at the right one.
- Redirect loop — 'too many redirects' in the browser
- 500 error across the whole site
- Permalinks returning 404 for every post
- HTTPS redirect not working, or forcing the wrong domain
- Old URLs not redirecting after a migration
What usually causes it.
In roughly the order I check them. Knowing the likely causes is what makes a fix fast rather than exploratory.
Conflicting redirect rules
Multiple plugins or manual edits each adding their own HTTPS or www rules. They fight each other and produce a loop.
Invalid directive or unsupported module
A directive referencing an Apache module the server does not have loaded causes an immediate 500 across the site.
Missing rewrite rules
The WordPress rewrite block deleted or overwritten, which breaks every permalink while the homepage still works.
Rule order
Redirect rules are evaluated in order. A catch-all placed before specific rules means the specific ones never run.
What the job includes.
- Current .htaccess audited line by line
- Conflicting and redundant rules consolidated
- Correct HTTPS and canonical domain handling in one place
- Permalink structure restored and verified
- Migration redirect map implemented properly where needed
- Backup of the previous file before any change
- 14-day correction guarantee
Questions, answered.
Why did a small change break everything?
Apache reads .htaccess on every request and rejects the whole file if any directive is invalid — so one bad line means a site-wide 500 rather than one broken feature.
I changed domain and lost my Google rankings.
That is almost always missing or blanket redirects. A proper page-by-page 301 map preserves link equity; redirecting everything to the homepage tells Google the content is gone.
Should redirects go in .htaccess or a plugin?
Server-level rules are faster and more reliable for canonical and HTTPS handling. A plugin is fine for content redirects an editor needs to manage. Mixing both for the same purpose is what causes loops.
Other Website & General fixes.
Website Down — Emergency Diagnosis
Site completely unreachable and you don't know why? I find out fast and get it back.
From $59PHP Error & Fatal Exception Fix
PHP warnings, deprecations or fatal errors showing on your site? Traced and fixed properly.
From $49Database Repair & Optimisation
Corrupted tables, crashed database or bloated tables slowing everything down? Repaired.
From $69Failed Migration Rescue
Moved hosts and now something is broken or missing? I finish the migration properly.
From $89Let's get it fixed.
Send the symptoms, when it started, and what changed just before. You'll get a straight answer and a fixed price — usually the same day.
Or book a slot directly — cal.com/