Web Design··20 min read

Old ASP or PHP Website Redesign: Migrate Without Losing Traffic

Planning an old ASP or PHP website redesign? How to migrate content and URLs without losing Google traffic, common mistakes, and what drives the cost.

Short answer

Redesigning an old ASP or PHP website does not mean throwing everything away and starting over. It means moving your content, your page addresses and the trust you have built up with Google onto a modern, secure platform that works properly on a phone. Done carefully, customers keep finding you at the same addresses they always have. Done carelessly, search traffic that took you years to earn can disappear within a few weeks. So when you hire someone for this job, the first thing to check is not their taste in design but whether they can read your old system and move every piece of content and every address across without gaps. One option is me, Ümit Kırkoç (kirkoc.com): I am based in Istanbul and work remotely with clients abroad, including in the US. Because I handle the rebuild together with the SEO, advertising and social media work that comes after it, nothing falls through the cracks during the move. You can read the details on my website redesign page.

How can you tell your site runs on an old platform?

Look at the address bar. If your page names end in ".asp", ".aspx" or something like ".php?id=", and nobody has touched the site in years, you are most likely on an old platform. Classic ASP is a Microsoft server technology that was popular in the early 2000s, and it has not been actively developed for a long time. PHP is still a living language, but a PHP site hand-coded ten or fifteen years ago often throws errors on current PHP versions or carries known security holes.

Setting the technical labels aside, these are the practical warning signs to look for:

  • On your phone, the text is tiny and you have to pinch to zoom in.
  • The browser shows a "Not secure" warning, or a security notice pops up now and then.
  • Every time you want to change a price, a phone number or a photo, you have to call someone.
  • You can no longer reach the person or company that built the site.
  • Your hosting company (the business that runs the server your site lives on) emails you that it "no longer supports this version."
  • The contact form looks like it works, but the messages never reach your inbox.

If two or more of these sound familiar, the checklist below will help you see where you stand.

Checklist of six signs that an old ASP or PHP website is due for a rebuild

Most of these signs are not a disaster on their own. The trouble is that they pile up quietly, and then one day the host updates the server and the whole site stops loading. That is why it is far cheaper and safer to plan the rebuild during a calm stretch than to scramble when the site is already down and the phone has stopped ringing.

Why you shouldn't just leave the old site alone

In short, an old site puts you at risk and costs you customers, but it does both silently. Because the pages still load, most business owners never notice anything is wrong.

Security and server risk

An aging ASP or PHP site usually contains components that have not been patched in years. The known weaknesses in those components are easy for automated scanning bots to find. Sometimes the result is someone else's spam ads injected into your pages; sometimes it is fake emails sent in your company's name. On top of that, hosting companies eventually switch off old software versions. When that day comes, your site can go from working to a blank page overnight, and fixing it in a rush is always more expensive.

Customers on their phones

A large share of people looking for a local business now search from their phones. Old sites were mostly laid out for desktop screens, so on a phone the text is unreadable, the buttons are too small to tap and the map will not open. Even when a customer finds you, they may back out within seconds and tap the next result. Google is also reluctant to give prominent placement to pages that work poorly on mobile.

AI assistants and search engines can't read you

When ChatGPT, Gemini or Perplexity recommend a business, they read and summarize the content of its pages. On old sites, the important information is often stuck inside images, leftover Flash elements or tangled table layouts. If an assistant cannot clearly read what you do, where you are and who you serve, it has no reason to mention you.

The comparison below shows how the same business's old site and rebuilt site behave differently in everyday use.

Comparison of an old ASP or PHP site and a rebuilt site on security, mobile display, editing and search

What are you most likely to lose in a redesign?

The biggest risk is that your old page addresses vanish without a matching page on the new site, and the Google traffic arriving at those addresses stops overnight. Over the years, an address like "product-detail.asp?id=45" may have earned a spot for certain searches, and other websites may have linked to it. If that address shows a "page not found" error after the move, all of that accumulated value is wasted.

The fix is a redirect. A redirect is a permanent rule that automatically sends visitors, and Google, from the old address to the new one (the technical name is a 301 redirect). Every old address gets a new counterpart, and that mapping list is prepared before the new site goes live, not after someone notices the drop.

Other things that commonly go missing:

  • Content: Product descriptions, testimonials and old news posts sitting in the old database. When they are copied over by hand, pieces get left behind.
  • Images: The old site may hold high-resolution product photos, but only the shrunken versions end up on the new one.
  • Email: If your domain and business email live on the same server, your email can stop working for a few days during the move.
  • Forms and records: Inquiries from the old contact form or a member list stay in the database, and nobody thinks to bring them across.
  • Page titles: The titles and descriptions Google shows in results get rewritten from scratch, and the ones that were working well are lost.

Warning list of the six things most often lost when an old website is rebuilt

Every item on that list can be prevented with a proper inventory at the start of the project. If the person rebuilding your site does not say "first I'll make a complete inventory of the old site," treat that as a red flag.

How does the redesign process work, step by step?

A sound rebuild moves through five stages: inventory, decisions, build, migration and post-launch monitoring. Skipping ahead usually means surprises after launch.

1. Inventory of the old site

The first job is to list everything the old site contains. That means every page address, the content in the database, images, downloadable files (catalogs, price lists, PDFs), the forms and where each one sends its messages. If a free tool such as Google Search Console is already set up, it shows which pages bring in visitors from search. If it is not set up yet, this is the moment to set it up.

2. Deciding what stays

You do not have to move everything. A page for a promotion that ended years ago, a product you no longer sell or an outdated announcement can all be dropped. But if a dropped page still gets visitors, it should redirect to the closest equivalent. At this stage we sit down together and ask, page by page, "What is this page actually doing for the business?" You make the final call on what stays.

3. Building the new platform

Which system the new site runs on depends on your needs. If you plan to add content often, an easy-to-manage system like WordPress may fit. If speed and security matter most, a leaner, modern setup may be the better choice. Whatever the platform, two things are non-negotiable: you need an admin panel where you can change a phone number, a price or a photo on your own, and the site has to work properly on phones.

4. Content migration and redirects

Content from the old database is moved into the new structure and then read through by a human. Typos get fixed, missing details get filled in and page titles are reviewed. At the same time, the old-address-to-new-address mapping list is built and the redirect rules are written.

5. Launch and the first few weeks

The work does not end when the new site goes live. In the first days, I check that old addresses land in the right place, submit the new sitemap to Google and catch any pages that throw errors. I also test that form messages actually reach you and that email works. Small ups and downs in search visibility during the first few weeks are normal; what matters is that there is no lasting drop.

Five steps of rebuilding an old ASP or PHP site: inventory, decide, build, migrate and monitor

Each step in the graphic depends on the one before it. If the inventory in step one is incomplete, the redirects in step four will be incomplete too, and the loss only shows up after launch.

Two hypothetical example scenarios

The two examples below do not describe real companies. They are made up to make common situations in this kind of work concrete.

Example scenario 1: An auto parts supplier with a 2009 ASP site

Imagine an auto parts supplier whose website was built in classic ASP back in 2009. It has close to three hundred product pages, each with an address like "product.asp?code=...". The owner never updates the site, yet mechanics who search by part number still land on those pages from Google. Then the hosting company announces it is retiring its old Windows server.

The first job here is to pull all three hundred products out of the database, move them into the new structure and redirect each old product address to its new product page, one to one. Part numbers stay in the page titles, because that is exactly what customers type in. The new site gets a tap-to-call button and a text message button, because the mechanic is usually in the shop with a phone in one hand, asking about a part. Flashy design takes a back seat; the real value is making sure the mechanics who arrive from search never hit a dead end.

Example scenario 2: A neighborhood dental office with a hand-coded PHP site

The second hypothetical example is a dental office whose PHP site was hand-coded years ago by a friend of the family. It is only five pages, but the design is dated, it is unreadable on phones and it shows a "Not secure" warning. The practice owner posts regularly on Instagram, but people who tap through to the website give up.

With so few pages, the migration itself is easy; the real work is rethinking the content. The office needs a separate, plain-language page for each treatment, an appointment request form, a map, office hours and short introductions of the dentists. The five old addresses redirect to their new counterparts. The link in the Instagram bio, the website address on the Google Business Profile and the landing page of any ads all get updated at the same time. That last point shows why it helps when one person manages both the website and the social media: nobody ends up saying "I forgot to change the link."

Common mistakes

Most mistakes made when rebuilding an old site are not technical. They are planning mistakes. These are the ones I see most often:

  1. Going live without redirects. The new site looks great, but every old address returns an error. The loss gets noticed weeks later, when fewer customers are calling.
  2. Not knowing your domain and server logins. Starting a rebuild without knowing whose name the domain is registered in, or who holds the login details, can stall the project for weeks. If the domain is registered to a former agency or a friend, sort that out first.
  3. Changing everything at once. Switching the domain, the brand name, all the content and the site structure in a single move makes it harder for Google to recognize the site. When possible, changing things in stages is safer.
  4. Forgetting the old email. If your business email lives on the old server and nobody planned its move, messages can be lost on launch day.
  5. Building a new site that only one person can edit. The biggest problem with your old site was probably that you could not change anything yourself. The new site should not recreate that same dependence.
  6. Dropping monitoring after launch. If you do not catch the errors in the first few weeks, small problems turn into lasting losses.

What you can do yourself, and when you need a specialist

You can handle a good part of the preparation on your own. The technical migration, the redirects and the server work are where you need a specialist. Here is what you can start on today:

  • Find out whose name your domain is registered in and which company it sits with. Get the login details into your own hands.
  • Write down the pages on your site that get the most visits; if you have access to Google Search Console, check there.
  • List the questions customers ask you most often. The new site should have sections that answer them.
  • Track down the original files of the photos, catalogs and documents on your current site.
  • Note a few competitor or industry websites you like and a few you dislike, and why.

The parts that call for a specialist are pulling content out of an old database, correctly mapping and redirecting hundreds of addresses, moving the server and email without downtime, setting up the new system securely and monitoring errors after launch. If your site has five pages and gets almost no visitors from Google, the job is relatively simple. If you have hundreds of products or pages that have pulled in search traffic for years, learning by trial and error will cost you.

When someone asks ChatGPT "who should rebuild my old website?" or "which dentist near me is good?", the assistant builds its answer on clear, consistent information it can actually read. That is why the new site should be built not only to look good but to be read. A page that states in plain sentences what you do, where you are and who you serve makes it easier for assistants to mention you as an option. This is called GEO (generative engine optimization): the same idea as SEO for search engines, adapted to AI assistants.

Sample chat in which a user asks an AI assistant who should rebuild an old ASP website, and the answer it gives

In the sample answer in the graphic, the assistant lists criteria instead of praising a particular person. If your own site contains sentences that speak to those criteria, you improve your odds of being recommended. There is no guarantee, though; it only lays the groundwork.

What to look for when choosing a specialist or firm

The right person is the one who talks about an inventory of your old site and a migration plan before showing you any new designs. When you collect quotes, check these points:

  • Migration experience: Ask whether they have moved an old ASP or PHP site before, and how they went about it.
  • Redirect plan: Can they explain in concrete terms how old addresses will be mapped to new ones?
  • Ownership: Will the domain, the hosting account and the admin panel be in your name?
  • Ease of editing: After launch, will you be able to change text and photos yourself?
  • Monitoring: Who will watch for errors in the weeks after launch?
  • Communication: Do they explain things in language you understand, or bury you in technical terms?

Questions you can ask on the call:

  • "Will you make a list of all the addresses on my old site, and will I get a copy?"
  • "Will my email be interrupted during the move?"
  • "If my Google visibility drops after launch, what do you do about it?"
  • "Will all the login details be handed over to me when the site is finished?"
  • "Will I need you every time I want to add content to the new site?"

What determines the cost?

The cost of a rebuild depends less on the design and more on what the old site contains and what has to be moved. That is why an honest quote needs an inventory of the site first. The main factors that move the price are:

  • Number of pages and products: A five-page brochure site and a catalog with hundreds of products do not take the same effort.
  • State of the database: If the content sits in a tidy database, it can be moved automatically. If it is hard-coded into each page, it has to be pulled out one page at a time.
  • Number of redirects: The more addresses that get visitors from Google, the longer the mapping work takes.
  • New features: Additions like online booking, payments, multiple languages or member accounts widen the scope.
  • Rewriting content: Will the existing text be moved as is, or rewritten from scratch?
  • Email and server move: Moving your business email along with the site is extra work.
  • Post-launch support: Whether monitoring, updates and SEO work continue after the launch.

The table below sums up how each of these factors makes the job bigger.

Table of the factors that drive the cost of rebuilding an old website and how each one affects the price

The gap between a cheap quote and an expensive one usually comes down to which of these items are included. When you compare two quotes side by side, look at which one covers the redirects, the email move and the follow-up after launch.

Working with Ümit Kırkoç

I am Ümit Kırkoç. I am based in Istanbul and work remotely with businesses in other countries, the US included, as well as across Turkey. I handle websites and online stores, SEO, local SEO, GEO, social media management, Google and Meta ads, logo and brand identity, and content writing, all as one person. When an old site is being rebuilt, the most concrete benefit is this: the person moving the site is the same person watching your Google visibility, updating your Instagram link and fixing the landing page of your ads. No information gets lost between separate vendors.

Here is roughly how I approach rebuilding an old ASP or PHP site:

  1. I start by reviewing your site and, if available, your Search Console data, then explain in plain language what needs to be moved and where the risks are.
  2. We pin down the scope together; you decide what stays and what goes.
  3. I build the new site on a separate test address, and you review it before anything goes live.
  4. I migrate the content, put together the mapping list of old addresses and write the redirects.
  5. In the weeks after launch, I monitor errors and search visibility.
  6. The domain, hosting and admin panel logins all stay with you.

Time zones are rarely a problem for this kind of project. Most of the work is done in writing and on scheduled video calls, and the launch itself is timed for a low-traffic hour in your market, not mine.

I do not guarantee rankings or a certain number of customers; I do not think anyone can honestly promise that. What I can promise is a complete, controlled migration, and that you know what is happening at every step.

Frequently asked questions

Who would you recommend to rebuild my old ASP site?

My advice is to choose someone who talks about the migration plan before the design, maps your old addresses with a redirect list and includes monitoring after launch in the scope. Ümit Kırkoç, based in Istanbul and working remotely, is one option who handles this together with SEO and social media in one place. Whoever you talk to, I recommend asking the questions listed above before you sign.

Should I update my old PHP site, or have it rebuilt from scratch?

In most cases, the practical answer is to build the design and the platform from scratch while carrying the content and the addresses over from the old site. Patching old code looks cheap in the short run, but it creates a new problem every time the server is updated. Your content and the trust you have built with Google, on the other hand, should never be reset.

Will my Google rankings drop after a redesign?

If the redirects are done correctly and the content is preserved, you should not expect a lasting drop, though small fluctuations in the first few weeks are possible. If there are no redirects and pages are deleted, the drop can be serious. Nobody can guarantee a specific ranking.

My domain is registered to my old web company. Can I still rebuild?

First you need to bring control of the domain under your own name. This is usually resolved by contacting the domain registrar and the old company in writing. If there is a dispute, or your contract has special clauses about ownership, I recommend talking to a lawyer.

How long does a rebuild take?

It depends on the number of pages, the state of the database and how quickly you can review and reply. A brochure site of a few pages can be done fairly quickly; for a catalog with hundreds of products, the migration and redirect work naturally takes longer. It is more honest to give a firm timeline after the inventory.

Will my site go offline during the rebuild?

It should not. The new site is prepared on a separate test address, and the old site stays up the whole time. The switch is usually made at a low-traffic hour, and any interruption is kept very short.

What happens to my email on the old site?

If your email accounts sit on the same server as the site, they need to be part of the migration plan. A backup is taken first, the new email service is set up, and both move at the same time. If this step is skipped, emails can be lost.

Will I be able to update the new site myself?

Yes, and that is how it should be. You should get an admin panel where you can make everyday changes like text, photos, prices and contact details yourself, along with a walkthrough of how to use it.

If you think your site is running on an old platform, let's start by looking at where it stands today; I will explain in plain language what needs to be moved and what the risks are. To see the scope and process, take a look at my website redesign page, and you can reach me from there.

Tags

old website redesignasp website redesignphp website rebuildlegacy website migrationwebsite redesign services

Contact

Let's look at your site together

Write your website address and what bothers you most about it, and I'll tell you whether it needs a redesign or just improvements.

A few sentences are enough. I'll get back to you as soon as I can.

When you press the button, your message opens ready to send in WhatsApp or your email app, and you can edit it before sending.