Manufacturers
A capability list and a specification before it is anything else, and both have to be text a buyer can search rather than a scan.
Manufacturers hosting
Greenville, SC
Web Hosting in Greenville, SC
A checklist arrives from head office in another country. It asks about cookie consent, where the data is held, which analytics run and who signed off the privacy page. Very little of it was written with a small American subsidiary in mind, and some of it does not apply to one at all. Working out which parts are law, which are group policy and which are noise saves more money than any hosting decision.
AldoMedia is not in Greenville. The work is done from Buffalo, New York. There is no South Carolina office, no local number, and nobody who is going to drive over and look at your screen. Registering a domain, setting hosting up, moving a site that already exists and supporting it afterwards all happen remotely, which is how hosting has worked for as long as it has existed.
The checklist that was written for somewhere else
Automotive and engineering work in this part of South Carolina is often done by an American company with a parent somewhere in Europe. That parent has a legal department, and the legal department has a web policy. It comes down the line as a form, with a deadline and no explanation, and the local office is left working out what a consent platform has to do with a site that sells castings to three customers.
The first thing worth separating is law from policy. European privacy rules bind a company established in the European Union, and reach a company outside it mainly where it offers goods or services to people in Europe or monitors their behaviour. A subsidiary here selling to American manufacturers, from a site written for American buyers, is often outside that, and your own lawyer is the one who settles it. The group can still require compliance as internal policy. That requirement is real, but it is a contract with the parent rather than an obligation to a regulator.
The distinction matters because it changes who you are talking to and what the answer costs. If it is law, you comply. If it is group policy, there is a conversation to be had about scope, and it is usually a short one once somebody explains that the site has almost no European visitors to consent to anything. Most local teams never have it, because nobody told them it was available.
There is a version of this that does apply, and it deserves naming rather than waving away. If the group's sales people use your pages to reach buyers in Europe, if an enquiry form collects names from there, if staff or applicant detail from a European office passes through anything you host, the picture changes. That is a question about who uses the site, and answering it honestly takes an afternoon.
Have somebody read the site properly
Send the address. We will tell you what your pages load from other companies, what that means for the form on your desk, whether the certificate is valid, and whether the text can be edited here or is locked in somebody else's tool.
Cookie banners, analytics and what the site is really loading
The commonest outcome of a group checklist is a consent banner bolted onto a site that did not need one, configured so that it blocks nothing. The banner appears, the visitor clicks accept because that is the only button that makes it go away, and the tracking has already loaded by then in any case. That satisfies a screenshot sent back to head office. It satisfies no rule anywhere.
A better starting point is the thing the form is really asking underneath, which is what your pages fetch from other companies. A supplier site that has passed through two agencies and a group rebrand carries more than anyone here remembers: an analytics tag, a second one nobody removed, a chat box nobody answers, an embedded map, an advertising pixel from a campaign that ended years ago. Every one is a request to somebody else's server, and several set cookies or record an address that identifies the visitor.
The order that actually reduces the problem
- List every request the site makes to somebody else's server. A browser's own developer tools show this without buying anything, and the list is nearly always longer than expected.
- Delete what is not being used. A pixel from a finished campaign, a chat box nobody staffs and a duplicate analytics tag are cost with no benefit to the reader.
- Keep what earns its place, and know what it stores. One analytics tool, set up to hold no more than you need, is a defensible answer to a questionnaire.
- Write the privacy page last, describing what is true after that clear out rather than what a template, or the wording head office sent down, says.
Taken in that order, the consent question usually shrinks to almost nothing, because a site that loads no third party tracking has very little to ask permission for. Taken in the usual order, a banner is bought first and the underlying site stays exactly as it was, which is the expensive version of the same afternoon.
One honest point about the analytics itself. Head office wants a number out of the site, and a supplier site produces too few visits for that number to be worth defending. Knowing which pages get read is worth having. Knowing the make of phone somebody used is not, and it is that half which creates the paperwork. Drop it and the report going upstairs gets no worse. None of this depends on a hosting plan, which is why the repair costs an afternoon rather than a monthly line. A valid certificate is still the floor, and SSL covers that separately.
Who holds the keys when the parent is in another country
Ownership of a website gets tangled in any American company. Add an overseas parent and it tangles in a different shape. The domain is often registered by a group technology department working in another language and another time. The hosting was probably arranged locally, years ago, by whoever was handy. The pages may sit inside a platform the group chose without asking anyone here.
Three questions settle it. Whose name is on the domain registration, and is the contact address one that somebody in this building still reads. Which account pays for the hosting, and who can log into it without asking permission. Can a person in this office correct a sentence on a page today, without raising a ticket that crosses an ocean.
That last one is the practical failure. An engineering team here that has to email a marketing department in another country to fix a tolerance printed on its own capability page will eventually stop asking, and the page goes stale in a way nobody ever decided to allow. That is not a complaint about group technology. It is what happens when a small change has a long route.
Check the registration before anything else, because it is the only piece that cannot be rebuilt from what is already live. If it sits in a group account, fine, so long as somebody here knows which account and who to ask. If it sits with a former agency, sort that out while everyone is still cordial. Taking over a website works through recovering each piece.
We will handle the move
Copy the site, test it on a temporary address, redirect every old address including the document files, repoint the domain last and leave the mail records untouched so nothing bounces. You keep working while it happens.
Moving a site without losing what other people link to
Most moves here are not a launch. A group decides to consolidate, an agency contract ends, or an invoice turns up that nobody can explain. The order is most of the job: copy the site, test it somewhere temporary, write redirects for any address that changes, and repoint the domain last, so there is never a window pointing at nothing. Website migration sets that sequence out properly.
Other people have quietly built your site into their own records. A customer's procurement system holds a bookmark. A certificate was emailed to a buyer with a direct address that now sits in somebody else's file. If those stop working after a move, the move failed, however good the home page looks.
Mail is where it genuinely goes wrong. In a business whose orders, drawings and schedules arrive by email, an hour of bounced mail costs more than a day of website downtime. Write down the existing mail settings before anything is touched and carry them across unchanged. Email migration covers keeping mail alive through the change.
One point applies specifically to a subsidiary. If the group is pulling the site onto a corporate platform, ask for an export of the content first, in ordinary files rather than screenshots. The capability text and document library on an established supplier site are usually the most valuable things it holds, and a consolidation is when they get quietly thrown away.
What gets billed alongside web hosting in Greenville, SC
The hosting line is rarely the interesting one. What sits around it, on the invoices we read here, is a domain renewal, a certificate probably included already, an editing subscription, a backup add-on and a consent platform bought to answer a questionnaire.
Some of it is worth keeping. A domain and a working certificate are not optional. Backups are worth paying for if somebody has ever tested restoring one, and worth cancelling if nobody has, which is what website backups is about. A consent tool earns its cost on a site that genuinely serves European visitors and is close to worthless on one that does not, which is a question of fact rather than opinion.
Spending more on the hosting itself is justified when customers log in, when the site carries a real document library, or when an hour offline stops work in the plant. Visitor numbers on a supplier site almost never justify it. What a website costs to run puts the whole picture in one place.
Trades we cover in this kind of economy
Three kinds of business whose websites carry the most weight in a supply chain economy, each with a page of its own.
Engineering firms
Drawings, certificates and method statements that customers link to directly, which means addresses that have to stay put through a move.
Engineering firms hostingTrucking companies
Schedules, compliance paperwork and a phone number that has to be right, on a site nobody has time to log into twice.
Trucking companies hostingEvery trade we cover is on hosting by industry, and every city on our locations page.
Common questions
Greenville hosting questions
A parent company in Europe sent us a web compliance form. Does GDPR apply to a subsidiary in Greenville?
Possibly not, and it is worth establishing that before buying anything. The European rules bind companies established there, and reach companies outside mainly where they offer goods or services to people in Europe or monitor their behaviour. A subsidiary selling to American customers from South Carolina, with a site written for American buyers, is often outside that. We are not lawyers, and this is the one question on this page worth putting to one rather than to a hosting company. What we can tell you is that the group may still require compliance as internal policy, which is a genuine obligation owed to the parent, and its scope is negotiable in a way a law is not.
Do we need a cookie banner on a site that only sells to American customers?
Often no. A banner means something only if it actually stops things loading until the visitor agrees, and most of the ones we are shown stop nothing at all. Before adding one, find out what the site loads from other companies. If the answer is a single analytics tool, there is very little to consent to, and a plain privacy page that says what you collect and gives people a way to ask about it is the substance of what American state privacy laws tend to want, though which of them reach a company your size is again a lawyer's question. If the answer is a chat box, two analytics tags and an old advertising pixel, remove those first. The banner is the last step, and on plenty of sites it is not a step at all.
The group wants our site moved onto a European host. Does where the server sits matter?
For how the site behaves, barely. A visitor in South Carolina loading pages from a server in Europe notices a small delay and nothing else, and even that can be reduced. For policy it sometimes matters, because a group rule about where data is held is easier to satisfy when the answer sits inside the group. Ask what the rule actually says. If it is about customer records rather than web pages, the hosting location may be beside the point, and you would be accepting a slower site to solve a problem you do not have.
Customers overseas download our engineering documents. Is that a data protection issue?
Downloading a file is not, by itself. What creates an obligation is collecting something about the person: a form demanding a name and company before a datasheet is released, a login, or tracking that records who fetched what. If the document simply sits at a stable address, there is nothing to look after. Once you put a gate in front of it, you hold enquiry records, and you should know where they go, how long they are kept and who can read them. Gate a document only where the sales benefit is real.
Start with an honest look at what you have
Tell us what your site runs on, who can edit it, and what the form from head office is actually asking for. We will tell you what to fix, what to leave alone, and whether the plan you are already paying for is the right one.
See hosting plans Get help choosing
Or call 716-771-2536. We are in Buffalo, New York, so we answer Eastern time.