GIS user technology news

News, Business, AI, Technology, IOS, Android, Google, Mobile, GIS, Crypto Currency, Economics

  • Advertising & Sponsored Posts
    • Advertising & Sponsored Posts
    • Submit Press
  • PRESS
    • Submit PR
    • Top Press
    • Business
    • Software
    • Hardware
    • UAV News
    • Mobile Technology
  • FEATURES
    • Around the Web
    • Social Media Features
    • EXPERTS & Guests
    • Tips
    • Infographics
  • Blog
  • Events
  • Shop
  • Tradepubs
  • CAREERS
You are here: Home / *BLOG / Around the Web / What Growing Businesses Should Settle Before a Website Redesign

What Growing Businesses Should Settle Before a Website Redesign

November 19, 2026 By GISuser

What happens to the pages that already bring in leads when the new site goes live? That question gets asked in the first week of a redesign, or it gets answered in the third month after launch by a drop in the Google Search Console graph.

A growing business has plenty to lose. The old site is small enough that nobody wrote down what each page does, and the team is busy enough that nobody has time to find out. Then an agency sends a handsome set of mockups, everyone nods, and the real decisions get made by default.

The decisions below are the ones to settle while changing them still costs a conversation instead of a rebuild.

Think of the list as a pre-flight check for whoever is paying for the project. None of it needs a specialist to understand. All of it is cheaper in week one than in month four, when the developer has moved on to another client and the staging site is gone.

Say what the new site is for

A brief that says “modern and clean” produces something modern and clean. Whether it books more consultations, sells more units or gets a tradesperson found in a city search is left to chance. Pick the one or two outcomes the site exists to produce and write them at the top of the brief: demo requests, quote forms, completed checkouts, calls from a Google Business Profile listing.

That sentence does real work later. When the designer wants a full-screen video on the homepage, you can ask what it does for the quote form. When someone proposes merging eight service pages into one, you can ask which of those eight pages brings in the calls today. If nobody can answer, that is the finding.

Decide who signs off, too. A redesign with five reviewers and no tiebreaker drifts toward whatever the loudest opinion in the room prefers. Name one person whose job is to hold the site to the written outcomes, and give them the authority to say that a feature does not make the cut.

Put search in the room before the wireframes

A designer drawing templates in Figma will not ask about heading hierarchy, URL depth or how a category page links to its children unless someone has said those things matter. That is the practical case for bringing SEO into project planning early, before the first wireframe is approved and while the structure can still bend.

It takes one meeting at kickoff and one review at the template stage. The person from search brings a short list: the pages that must keep their addresses, the templates that need room for a real H1 and a few paragraphs of text, and the questions buyers type into Google and ChatGPT that the new site should answer in plain sentences.

Without that list, the trade-offs get made silently. A carousel replaces the paragraph of text that explained the service. A clever menu hides the sub-pages behind a hover state. Each choice looks fine on a slide, and each one removes something a search engine or an answer engine was using.

Inventory what already earns its place

Export the pages from Search Console by clicks and from GA4 by conversions, and put the two lists side by side. A page with modest traffic and a strong conversion rate is the one a redesign damages first, because nobody on the project notices it. Run a crawl with Screaming Frog to catch the pages that no menu links to but other sites do.

Ask sales which pages prospects mention on calls. Ask the owner which page they send to a referral. Then open ChatGPT and Perplexity, ask the questions your customers ask, and note which of your pages get cited. Those pages go on a protected list, and the protected list goes into the brief.

Record the current state before anything moves. Save the ranking pages, the title tags, the load times from PageSpeed Insights and the lead counts per month. Six weeks after launch you will want to know whether a dip is a seasonal pattern or a break, and a screenshot from the old site is the only honest comparison.

Map every old address to a new one

Each URL that changes needs a 301 redirect to its closest new equivalent. That is a spreadsheet job and it belongs to a named person: old address in column A, new address in column B, a note on why it moved.

Some moves are forced. Shopify builds addresses with prefixes such as /products/ and /pages/, so a migration from WordPress or Webflow changes URLs whether anyone wanted that or not. Others are choices, like shortening slugs because the new design looks tidier. Keep the old structure wherever there is no reason to change it. Where a change is needed, test the map with a crawl on staging before launch day, and check that no redirect points to another redirect.

Do not forget the addresses that are not pages. PDFs, image URLs, old campaign landing pages and the blog’s category archives all collect links over the years, and they are the ones that fall off the spreadsheet because nobody thinks of them as pages. The crawl and the Search Console export between them cover the bulk of that, and a quick look at the referral report in GA4 catches the rest.

What the new templates must carry over

The old theme did jobs nobody listed, and they disappear with it. Confirm that the new templates keep these three:

  • A page title and meta description for each URL, written by a person, with no theme default left in place
  • Structured data, such as schema.org Organization, LocalBusiness or Product markup, that lived in an old plugin
  • Body text that is real text on the page, because copy baked into an image, or loaded only after a script runs, may never reach a crawler that does not run scripts

Check them on a staging page by viewing the source and reading what is there. A page that looks right in the browser can be close to empty in the source.

Check who is allowed to read the new site

Staging sites carry a noindex tag or a Disallow rule in robots.txt so they stay out of search. When the site is pushed live, that setting travels with it more easily than anyone admits, and a live site that tells every crawler to stay away loses its rankings quietly.

While the file is open, decide on purpose what to do about AI crawlers. A rule for GPTBot or PerplexityBot is a business decision about whether your pages can be read and cited in answers, and it should be made by a person, not inherited from a template. Look at the CDN or firewall too. A bot-protection setting in Cloudflare can block a crawler that robots.txt allows.

Ask the developer to send you the final robots.txt as plain text on launch morning, and read it yourself. It takes two minutes. It is also the check that catches a staging Disallow rule before Google reads it.

Separate the parts that stay true from the parts that change

A service page carries two kinds of content. The explanation of what you do and who it helps stays put for years. The pricing, availability, version numbers and opening hours shift every quarter. Mixed into one block of copy, the second kind makes the first look stale, and every update means editing a page that was fine.

Settle the layout for splitting pages into an evergreen core and a current-state module while the designer still has room to give the changing parts their own block, with a visible last-updated line. The editor on WordPress or Webflow then touches one module on the first of the month and leaves the core alone. The visitor, and any answer engine reading the page, can tell which part is current.

Name an owner for launch week

Redesigns have a launch day and a launch month, and the second is where problems surface. Give one person the job. On day one they submit the XML sitemap in Search Console, spot-check twenty old addresses for correct redirects, and inspect the homepage with the URL Inspection tool. In the first fortnight, they watch 404 errors daily and compare Core Web Vitals in PageSpeed Insights with the old site’s numbers. Anything that slipped through gets a ticket with a name and a date on it, so the fix does not wait for the next quarterly review.

Before the next design meeting, open a spreadsheet, export your top pages from Search Console, and add a column headed “new URL”. Fill it in before any mockup gets approved. Whatever you cannot fill in is the part of the redesign nobody has thought through yet.

Filed Under: Around the Web

Top Press

The Global Expansion of Aueshah: A New Era of High Jewelry

April 11, 2026 By GISuser

KARACHI, PAKISTAN. The international luxury market is experiencing a profound shift. Consumers are increasingly rejecting mass-produced goods in favor of rarity, authenticity, and emotional depth. … [Read More...]

State of Data Science Report – AI and Open Source at Work

September 10, 2025 By GISuser

AI and Open Source at Work … [Read More...]

Topcon Announces Landmark Expansion of Topnet Live Network Across USA

January 26, 2025 By GISuser

LIVERMORE, Calif.---Topcon Positioning Systems has announced a significant expansion of its Topnet Live reference station network, introducing 200 new geodetic stations strategically positioned across … [Read More...]

Space Flight Laboratory (SFL) Announces Launch and Deployment of NorSat-4 Maritime Monitoring Microsatellite

January 19, 2025 By GISuser

Seventh Satellite Developed by SFL for Norway … [Read More...]

HERE and BMW Group extend partnership on AI-powered mapping system

January 8, 2025 By GISuser

HERE and BMW Group extend partnership on AI-powered mapping system for automated driving and enhanced road safety … [Read More...]

Everest Base Camp Helicopter Tour, Helicopter Return Trek, and Manaslu Circuit Trek: Which Nepal Adventure Is Right for You?

November 6, 2026 By GISuser

Almost everyone planning a Nepal trip runs into the same wall. You want the big mountains, you have a fixed number of days, and every itinerary you read seems to promise something … [Read More...]

SFL Missions Inc. Confirms Successful Deployment of Six HawkEye 360 Radio Frequency Detection Satellites with Advanced Capabilities

October 27, 2026 By GISuser

MĀHIA, New Zealand, 26 October 2026 – SFL Missions Inc. today confirmed the successful deployment of six radio frequency (RF) detection and geolocation satellites for HawkEye 360 … [Read More...]

Canadian-Built RoadEng 12 Uses AI to Find the Best Location for New Resource and Rural Roads

October 17, 2026 By GISuser

Vancouver, BC, Canada, October 15, 2026 – North Vancouver-based Softree Technical Systems today released RoadEng Version 12, used in more than 75 countries to locate and design … [Read More...]

Beyond the Map: How AI Image and Video Generation Is Changing Geospatial Communication

October 14, 2026 By GISuser

Ask anyone who has shipped a GIS project what the hardest part was, and the answer is rarely the spatial analysis. It is almost always the communication. A site suitability … [Read More...]

From Maternity to Everyday Wear: Building a Wardrobe That Grows With You

October 14, 2026 By GISuser

When I think about maternity clothing, I feel the biggest mistake is buying too many things at once. During pregnancy, your body keeps changing, and something that fits well today … [Read More...]

Copyright gletham Communications 2015 - 2026

Go to mobile version