1 |
On 29/09/2015 22:19, J. Roeleveld wrote: |
2 |
> On 29 September 2015 22:00:58 CEST, Tanstaafl <tanstaafl@×××××××××××.org> wrote: |
3 |
>> Hi all, |
4 |
>> |
5 |
>> I am not a web (or SEO) guy, but I manage our DNS and have for a long |
6 |
>> time. |
7 |
>> |
8 |
>> The boss has contracted with a web development company to do a full |
9 |
>> redesign of our website. |
10 |
> |
11 |
> Good luck with that. Hope you found a good company. :) |
12 |
> |
13 |
>> Our website has hundreds of thousands of pages, and years of SEO behind |
14 |
>> it. The guys who was her until recently was adamant that we must be |
15 |
>> very |
16 |
>> carefl with the redesign so as not to totally break SEO, and possibly |
17 |
>> getting blacklisted by Google. |
18 |
> |
19 |
> I never did anything with SEO. Would a mistake with that really get a site blacklisted? |
20 |
> |
21 |
>> The web developers are insisting that they need full access to our DNS |
22 |
>> (hosted by DNSMadeEasy), and the only reason I can think of for this is |
23 |
>> they plan on setting up HTTP redirects (DNSMadeEasy equivalent of a 301 |
24 |
>> redirect) for these pages - but hundreds of thousands of them? |
25 |
> |
26 |
> Redirects with DNS? |
27 |
> I can only think of adding subdomains (like about.example.com or similar) |
28 |
> |
29 |
>> Wouldn't this be better done at the web server level? Or am I just |
30 |
>> ignorant? |
31 |
> |
32 |
> Page redirects are, afaik, only possible with a webserver. They are part of the HTTP protocol. |
33 |
> |
34 |
>> Would love to hear experiences (good and bad), and a recommendation for |
35 |
>> what I should do. |
36 |
> |
37 |
> I would ask them what they actually want to achieve. Don't forget that your email and all other services are dependent of the DNS settings. |
38 |
> I can't think of many companies allowing a supplier for a website full access to a different part of the infrastructure. |
39 |
> |
40 |
> Most companies I deal with wouldn't even let the people responsible for the databases to reconfigure the storage for said database directly. |
41 |
|
42 |
I agree with Joost, needing access to all your DNS is off-the-wall. Any |
43 |
changes they need done, and they will be few, can be given to you as a |
44 |
support ticket for action just like everyone else gets to do. |
45 |
|
46 |
I would also have them specify exactly in their proposal what they |
47 |
intend to do, with full engineering. Any sane service provider will do |
48 |
that in their tender, and yours looks like a rather big tender. |
49 |
|
50 |
Lastly, get a second opinion of the changes they make. SEO tweaks can |
51 |
very easily get you blacklisted on search engines and a lot of methods |
52 |
out there are interpreted by Google as being dodgy. |
53 |
|
54 |
|
55 |
-- |
56 |
Alan McKinnon |
57 |
alan.mckinnon@×××××.com |