Yes, and a reputable one should fix its own technical errors at no extra charge. When an SEO company makes a change to your site and that change breaks something, the responsibility for correcting it sits with the company that made the change. This is not a favor or a goodwill gesture. It is a basic part of doing the work competently. The point of hiring a professional is that the work is done correctly, and that includes cleaning up any problem the work itself introduced.
What counts as an error they caused
Technical SEO work involves direct changes to your site: editing meta tags, adjusting redirects, modifying the robots.txt file, changing canonical tags, updating site structure, or altering page templates. Any of these can be done incorrectly. A redirect can point to the wrong page. A noindex tag can be applied to a page that should rank. A robots.txt rule can block pages from being crawled. If a problem appeared right after the company made a change, and the change is the cause, that is an error they caused.
This is different from a problem the company inherited or one created by another vendor, your developer, or a platform update. Honest companies distinguish between the two. They should be able to look at their own change log and tell you plainly whether the issue traces back to their work.
What a professional response looks like
A reputable company diagnoses the issue, explains what happened in plain terms, and corrects it without adding it to your invoice as new work. You should not be billed for fixing a mistake you paid them to avoid. You should also not be made to feel that raising the issue is unreasonable. Clear communication matters here as much as the fix itself. A company that admits the error, describes the cause, and confirms when it is resolved is behaving the way you want a vendor to behave.
Good companies also work in ways that reduce the chance of these problems. Testing changes in a staging environment before they go live catches many errors before they affect your real site. Keeping a change log, a dated record of what was changed and when, makes it straightforward to identify and reverse a faulty change. Industry guidance on technical SEO stresses that fixes are only useful when they are actually implemented correctly and tracked, not just recommended. Ask whether a prospective company uses staging and keeps a change record. These are signs of a careful operation.
What the contract and professionalism imply
Most SEO contracts define a scope of work, the specific services the company has agreed to deliver. Performing that work to a competent standard is part of the agreement, whether or not the contract spells out error correction word for word. A company that delivered a faulty change has not yet completed its obligation, so correcting it falls within the original engagement rather than being billable extra work. If your contract addresses revisions, change orders, or quality standards, review those terms, and keep in mind that verbal agreements are weaker than written ones. For any future changes, a brief written confirmation of what will be done protects both sides.
Professionalism fills the gap the contract leaves. A company that respects its clients takes responsibility for its mistakes without being pushed to. How a company handles its own error tells you a great deal about whether it is worth keeping.
How to raise it
Raise the issue directly and in writing. Describe what you observed, when you noticed it, and which change you believe is connected. Ask the company to investigate and confirm the cause. Request a clear timeline for the fix and written confirmation once it is resolved. Keep your own records of the messages.
If the company refuses to acknowledge a clear error, tries to bill you for repairing its own mistake, or cannot explain what it changed, treat that as a warning sign. A company that will not stand behind its work is one to reconsider. A company that owns the error, fixes it promptly, and explains how it will prevent a repeat is showing you exactly the accountability you should expect.