Author: ecoadmin

  • WooCommerce Website Cost

    In short: WooCommerce website cost is not zero: WooCommerce itself is a free WordPress plugin, but a live store still costs money. WooCommerce’s own pricing materials place hosting for most stores around $25–$350 per month and extensions around $29–$299 per year each, with card processing commonly near 2.9% + $0.30 per US transaction through WooPayments. Build labor follows broader US web project bands. Use the ranges below as market context, not Eco Digital quotes.

    Queries for woocommerce website cost, and Autocomplete phrases like “how much does woocommerce cost,” show up because the free plugin sticker hides hosting, extensions, payments, and design labor. Eco Digital scopes stores through WooCommerce development.

    US market price table (typical ranges)

    Path Typical US market range What you usually get Source
    WooCommerce software $0 platform fee for the core plugin Core ecommerce on WordPress WooCommerce pricing
    Hosting for most stores About $25–$350 per month Performance scales with traffic WooCommerce pricing
    Extensions About $29–$299 per year per extension Shipping, subscriptions, CRM, and other add-ons WooCommerce pricing
    Card processing (WooPayments example) About 2.9% + $0.30 per transaction Payment acceptance fees WooCommerce pricing
    Professional build labor (US market context) Many WordPress pros report average projects $2,500–$4,999; Clutch web projects often under $10,000 though averages run higher Theme/custom store design and launch Admin Bar 2025; Clutch
    Managed WordPress hosting reference Single-site plans from about $35 per month Managed WP hosting example Kinsta pricing

    WooCommerce’s pricing page also contrasts platform fees against hosted SaaS ecommerce tools and emphasizes that merchants choose their own host and extensions (WooCommerce).

    Free plugin, paid store

    Calling WooCommerce “free” is accurate for the core plugin and inaccurate for a production store. You still pay for a domain, hosting, a theme or custom design, essential extensions, SSL, and payment processing. Labor to configure catalog structure, tax, shipping, and checkout testing is usually the largest launch line for non-DIY teams.

    If you are choosing platforms, read WordPress vs Shopify before locking a budget shape.

    What moves a WooCommerce website quote

    Catalog complexity

    Variant rules, custom product data, and large catalogs expand import, template, and QA time. A 20-product catalog is not priced like a 2,000-SKU catalog with overlapping attributes.

    Checkout and shipping rules

    Table-rate shipping, subscription logic, deposits, and multi-currency needs often require paid extensions in the $29–$299 per year band each (WooCommerce). List them before comparing build bids.

    Integrations

    ERP, inventory, email, and fulfillment tools add mapping work. Late integrations are a common change-order source after design is approved.

    Care and update risk

    Stores need careful plugin updates because checkout failures cost revenue. Budget ongoing care using website maintenance cost and the WooCommerce SEO checklist for launch hygiene.

    DIY, freelancer, and agency paths

    DIY fits technical owners who can configure hosting, extensions, and taxes. Freelancers fit smaller catalogs with standard shipping. Agencies fit complex catalogs, custom checkout rules, migrations, and stores that need SEO-safe launches. Admin Bar’s WordPress project bands and Clutch’s web project data provide labor context, while WooCommerce’s own page covers platform fees (Admin Bar; Clutch; WooCommerce).

    How to compare WooCommerce quotes fairly

    1. Same catalog size and variant rules
    2. Same extension list with annual fees noted
    3. Same payment and shipping assumptions
    4. Same migration and redirect ownership
    5. Who owns hosting, admin, and extension renewals

    Sacramento retailers pairing local pickup with online checkout can also review Sacramento web development.

    Year-one planning worksheet

    Separate four buckets on a spreadsheet before you compare store quotes. Bucket one is platform and hosting fees using WooCommerce’s published hosting band of about $25–$350 per month (WooCommerce). Bucket two is extension renewals using the $29–$299 per year range per extension. Bucket three is payment processing as a percentage of sales. Bucket four is build and migration labor using Admin Bar and Clutch market context. Stores that mix those buckets into one undifferentiated number make vendor comparisons noisy.

    For SEO after launch, use the WooCommerce SEO checklist so product and category templates are not an afterthought.

    Related cost guides

    Next step

    Bring catalog size, shipping rules, and must-have extensions to discovery. Eco Digital maps the store on WooCommerce development and separates platform fees from build labor in the quote.

    Frequently Asked Questions

    How much does a WooCommerce website cost?

    Core software is free, hosting for many stores is published around $25–$350 per month, extensions often run $29–$299 per year each, and payment fees commonly sit near 2.9% + $0.30 per transaction (WooCommerce). Build labor is additional.

    Is WooCommerce cheaper than Shopify?

    It depends. WooCommerce has no core platform fee but shifts hosting, extensions, and maintenance onto you. Compare total year-one cost, not only monthly platform stickers. See WordPress vs Shopify.

    Do I need paid extensions?

    Many stores need at least a few for shipping, subscriptions, or CRM connections. Budget using WooCommerce’s published $29–$299 per year extension band (WooCommerce).

    Are payment processing fees included in build quotes?

    Usually not. Processing fees are ongoing transaction costs separate from design and development.

  • WordPress vs Shopify: Which Is Better for Your Business?

    In short: WordPress vs Shopify comes down to ops: pick Shopify when you want a commerce-first hosted platform with less server responsibility. Pick WooCommerce when you want WordPress content flexibility and are ready for hosting, plugin, and care ownership. The better store is the one your team can operate safely after launch.

    Eco Digital builds WooCommerce stores and works across website platforms for content-led businesses. We also advise when Shopify is the cleaner commerce fit. This comparison is intentionally balanced. If you need implementation, see WooCommerce development and the broader website development pillar.

    Quick comparison table

    Factor Shopify WooCommerce (WordPress)
    Hosting Platform-hosted You choose hosting
    Primary strength Commerce operations Content + commerce on one CMS
    App / plugin model Shopify app ecosystem WordPress plugin ecosystem
    Theme customization Themes + Liquid / Hydrogen stack depending on build PHP themes, builders, custom code
    Ongoing ops App and theme updates inside Shopify Core, plugin, theme, server care
    Typical fit Product-led stores, lean ops teams Content-heavy brands, WP-centric teams

    Choose Shopify when…

    • Checkout reliability and commerce tooling are the main product
    • You do not want to manage WordPress updates and server patches
    • Your catalog and discount rules fit Shopify’s model well
    • Your team prefers one vendor admin for store ops

    Choose WooCommerce when…

    • Your blog, resources, and store must live in one WordPress editorial workflow
    • You need deep CMS flexibility around non-product content
    • You already have WordPress expertise in-house or via an agency care plan
    • Custom data models fit WordPress better than forcing a SaaS storefront

    If you need a fully custom commerce experience beyond either platform’s comfort zone, look at custom or full-stack options after discovery, when the brief needs it.

    Total cost of ownership (without invented prices)

    Compare three years, not month one:

    • Platform subscription or hosting
    • Theme and app/plugin fees
    • Payment fees
    • Agency or developer retainers
    • Maintenance and security time
    • Migration cost if you outgrow the first choice

    Shopify often fronts more as platform fee and less as server care. WooCommerce often fronts less as “platform brand” and more as hosting + plugins + maintenance labor. Neither is free.

    SEO differences that actually matter

    Neither platform “wins Google” by logo.

    What matters:

    • Clean product and category information architecture
    • Indexation control for filters and parameters
    • Fast, usable templates
    • Unique product content
    • Sensible internal links from content to categories

    WooCommerce teams should follow a store checklist like our WooCommerce SEO checklist. Shopify teams still need canonical discipline and app bloat control. Content quality guidance from Google remains platform-agnostic (helpful content).

    Migration reality check

    Moving Shopify → WooCommerce or the reverse is a rebuild of templates, URLs, apps, and often customer accounts. Budget for:

    Do not migrate for aesthetic reasons alone.

    Ops burden: the deciding factor for many SMBs

    Ask your future operator:

    1. Who applies updates next Tuesday?
    2. Who tests checkout after those updates?
    3. Who owns backups and restores?
    4. Who fixes the broken discount app during a sale?

    If the clear answer is “nobody,” prefer the platform that reduces moving parts, or buy a real maintenance plan.

    How we recommend a side without fan fiction

    Our discovery order:

    1. Catalog complexity and checkout requirements
    2. Content model (store-only vs magazine + store)
    3. Operator skill and care budget
    4. Integration list (ERP, CRM, subscriptions)
    5. SEO constraints and existing URL equity

    Then we recommend Shopify, WooCommerce, or another stack: and we say when we are not the right builder.

    Local / Sacramento note

    If you are a Sacramento retailer or service brand adding ecommerce, keep local entity pages truthful and separate from thin doorways. See Sacramento web development.

    Content model examples (to make the choice concrete)

    Mostly products, light blog: Shopify usually wins on operational simplicity.

    Editorial brand with a shop attached: WooCommerce (or Shopify plus a separate content CMS) needs an explicit content plan. Many teams underestimate the cost of splitting blog and store across vendors: or the plugin weight of keeping both in WordPress.

    Subscriptions, bundles, wholesale portals: Validate with a proof-of-concept on both platforms before you redesign the brand. App coverage differs, and “the app exists” is not the same as “the app is stable at your order volume.”

    Payment and checkout considerations

    Checkout friction loses sales. Evaluate:

    • Guest checkout options
    • Express pay methods your customers expect
    • Tax and shipping rule complexity
    • Multi-currency needs
    • Fraud tools

    Shopify’s hosted checkout is a major product feature. WooCommerce checkout quality depends heavily on theme, gateway, and plugin choices: another reason supervised maintenance matters after launch.

    Staff skills matrix

    Skill needed Shopify-leaning team WooCommerce-leaning team
    Theme tweaks Shopify theme / Liquid familiarity WordPress theme / builder skills
    Catalog ops Strong native admin patterns Products + WP editorial habits
    Security / hosting Mostly platform-managed Host + plugin vigilance required
    Custom features Apps + Shopify development Plugins + custom PHP/JS or headless

    Hire for the matrix you choose. Buying Shopify and hiring only WordPress specialists (or the reverse) creates avoidable delay.

    International and tax complexity

    If you sell across jurisdictions, validate:

    • Tax automation quality
    • Duties/shipping rules
    • Multi-currency presentation
    • Language needs (store vs separate localized sites)

    Platform marketing pages make this look easy. Real catalogs with mixed digital and physical goods still need a configuration workshop before theme design starts.

    Headless and composable caveats

    Both ecosystems offer headless options. They can be right for brands with strong engineering teams and clear performance goals. They are usually wrong as a first storefront for a small business that mainly needs reliable checkout and simple content edits. If a proposal leads with headless jargon before catalog and ops discovery, slow down. Composable stacks raise capability and raise the cost of every future change.

    Practical next step

    Score Shopify vs WooCommerce on catalog complexity, content model, and who will test checkout after updates. Pick the winner on ops reality. Then budget three-year ownership, not only launch week. If WooCommerce fits, talk to us about WooCommerce development. If Shopify fits, we will say so rather than force WordPress. We recommend the fit we would use ourselves.

    Frequently Asked Questions

    Is WooCommerce free?

    WooCommerce software is open source, but hosting, themes, premium plugins, development, and care are not free. Compare total cost.

    Is Shopify easier than WooCommerce?

    For many pure stores, yes: especially if you do not want server management. Complex content models can still favor WordPress.

    Which is better for SEO?

    Neither automatically. Architecture, content, and technical hygiene decide outcomes.

    Can I switch later?

    Yes, with a migration project. Plan redirects and expect rebuild effort.

    Do you build Shopify and WooCommerce?

    We build WooCommerce and advise across platforms under our website development services. Ask in discovery which implementation path we recommend for your catalog and team.

  • WordPress Website Cost

    In short: WordPress website cost is not zero: WordPress software is free, but a finished business website is not. In the 2025 Admin Bar survey of WordPress professionals, 38.2% reported average website project prices of $2,500–$4,999, with another 20.4% at $5,000–$9,999. Managed WordPress hosting examples start around $35 per month, and US agency design rates commonly fall around $100–$149 per hour. Use these as market bands, then request a scoped quote.

    People looking up wordpress website cost, including yearly or country-specific Autocomplete variants, want planning numbers. Published survey and hosting data help. Those figures are market bands, not Eco Digital prices. WordPress builds are scoped through WordPress development.

    US market price table (typical ranges)

    Path Typical US market range What you usually get Source
    WordPress software $0 for WordPress.org core Self-hosted CMS software WordPress.org (software is free; hosting separate)
    WordPress professional average project price $2,500–$4,999 modal band (38.2%); $5,000–$9,999 next (20.4%); $1,000–$2,499 for 22.8% Designed business site on WordPress Admin Bar 2025 WordPress Professionals Survey
    Clutch-reviewed web design projects Average about $38,105; most under $10,000 Broader web design market mix Clutch Web Design Pricing Guide
    US agency hourly rates Commonly $100–$149 per hour Design/dev labor Clutch
    Managed WordPress hosting Single-site plans from about $35 per month Hosting, CDN, backup tooling examples Kinsta pricing
    Care / maintenance retainers Often $50–$500+ per month by tier Updates, backups, monitoring Pronto maintenance ranges

    Admin Bar also reports a median WordPress professional hourly rate around $95 and an average around $96.36 in the same survey (Admin Bar 2025).

    Free software, paid launch

    WordPress.org being free does not mean a business website costs $0. You still need hosting, a domain, a theme or custom templates, essential plugins, and someone to design, build, migrate, and maintain the site. DIY builders can keep cash costs closer to hosting and plugins. Hired help follows the project bands above.

    If you are weighing WordPress against hosted builders, see WordPress vs Squarespace vs Wix for small business and is WordPress good for SEO.

    What moves a WordPress website quote

    Theme versus custom templates

    A lightly branded theme costs less than unique templates built for your sitemap. Price the unique layouts when you compare bids. Related reading: hire a WordPress developer: what to ask.

    Plugins and integrations

    SEO, forms, membership, and CRM plugins can be free or paid. Complex integrations need discovery and QA beyond the plugin price.

    Content and migration

    Imports, redirects, and content cleanup often rival design hours on redesigns or platform moves. Pair with website redesign cost when replacing an old site.

    Ongoing care

    After launch, budget updates and monitoring. Pronto’s US maintenance bands of about $50–$150 basic, $150–$500 standard, and $500–$2,000+ premium help separate care from build (Pronto). Also see website maintenance cost.

    DIY, freelancer, and agency paths

    DIY fits owners comfortable with hosting, themes, and plugin hygiene. Freelancers fit brochure and small-business sites inside Admin Bar’s common project bands. Agencies fit multi-template systems, ecommerce, and migrations that need SEO launch hygiene. Clutch’s note that many reviewed projects cost less than $10,000 is useful context beside Admin Bar’s WordPress-specific distribution (Clutch; Admin Bar).

    How to compare WordPress quotes fairly

    1. Same sitemap and unique-template count
    2. Same plugin and integration list
    3. Same content and migration ownership
    4. Same hosting assumption for year one
    5. Who owns admin, updates, and backups after launch

    For Sacramento businesses standardizing on WordPress for local service pages, see Sacramento web development.

    Year-one WordPress budget shape

    A practical year-one plan uses four lines. First, build labor using Admin Bar’s common $2,500–$4,999 or $5,000–$9,999 project bands (Admin Bar 2025). Second, hosting using managed examples from about $35 per month (Kinsta). Third, premium plugins and a theme if you are not building fully custom templates. Fourth, care using Pronto’s basic-to-standard monthly bands (Pronto). That shape answers Autocomplete questions about WordPress website cost per year without inventing one fake total.

    When ecommerce is required, switch the labor assumptions to the WooCommerce website cost guide so catalog and checkout complexity are priced explicitly.

    Related cost guides

    Next step

    Bring a sitemap, plugin must-haves, and hosting preferences to discovery. Eco Digital maps the build on WordPress development and quotes from that written scope rather than a generic band.

    Frequently Asked Questions

    How much does a WordPress website cost in the USA?

    Many WordPress professionals report average project prices of $2,500–$4,999, with another large group at $5,000–$9,999 (Admin Bar 2025). Hosting and care are usually extra.

    Is WordPress free?

    The WordPress.org software is free. Hosting, domains, premium themes/plugins, design labor, and maintenance are not.

    How much does WordPress hosting cost?

    Managed examples such as Kinsta publish single-site plans from about $35 per month (Kinsta). Shared hosts can be cheaper with fewer managed features.

    Does WordPress cost more than Wix?

    Not always. Wix bundles hosting into plan fees, while WordPress shifts hosting and care onto you. Compare year-one totals, including labor. See how much a Wix website costs.

  • Web Developer vs Web Designer vs Full-Stack: Who Do You Hire?

    In short: In a web developer vs web designer choice, hire a web designer for structure, visuals, and interaction design. Hire a web developer to implement sites and integrations in code or a CMS. Hire full-stack when front end and back end application work must ship together. Many projects need more than one role under a single agency SOW.

    Eco Digital staffs across these skills for website development, custom website development, and full-stack development.

    Role map

    Role Primary outcomes
    Web designer UX flows, visual system, UI states, design QA
    Web developer CMS/theme implementation, front-end build, integrations
    Full-stack UI plus server, data, APIs, deployment

    Typical hire patterns

    • Brochure site on WordPress/Wix: designer + WordPress/Wix developer, or an agency pod
    • Brand-sensitive marketing site: stronger design lead, developer implementing components
    • Customer portal: full-stack leadership with design support
    • Store: developer experienced in WooCommerce or Shopify plus UX for product templates

    Job titles are messy in the market

    Freelancers may blend roles. Ask for artifacts: Figma files, repos, staging URLs, and SOWs from similar projects. Use the hire a WordPress developer question list when WordPress is in play.

    How agencies package this

    Agencies often sell outcomes (a launched site) rather than hours by title. Still ask who leads design decisions versus engineering decisions, and who is on after launch for website maintenance.

    Sacramento buyers

    If local presence matters, confirm the team will keep GBP and site NAP aligned: Sacramento web development.

    Interview prompts that reveal real experience

    Ask designers to walk through a messy feedback cycle. Ask developers to explain a production incident they fixed. Ask full-stack candidates how they split front-end and API work in their last release. Stories beat buzzwords.

    Agency pods versus separate contractors

    Separate freelancers can work if you provide project management. If you cannot, buy a pod that already includes design, development, and a single accountable lead. Coordination cost is real even when hourly rates look lower on paper.

    Portfolio signals that matter in interviews

    Designers should show messy feedback cycles and how they resolved them. Developers should show a production incident and the fix. Full-stack candidates should show how they split API and UI work in one release. Artifacts beat adjective-heavy résumés.

    How Eco Digital assigns leads

    Commercial marketing sites often have a design lead and a WordPress lead. Application-like builds have a technical lead from the full-stack side. SEO ops advises on information architecture and launch hygiene. Buyers should ask who the single accountable lead is for timeline and quality, even when multiple crafts are involved.

    Budget allocation examples (factors, not prices)

    A marketing site might allocate more to design and CMS implementation. A portal might allocate more to back-end and security testing. Ask vendors to show allocation by craft in the proposal. Allocation reveals whether your money funds the riskiest parts of the work.

    Decision tree for a first hire

    If visuals and UX are blocking launch, prioritize design. If a theme exists and forms are broken, prioritize development. If you are building authenticated workflows with custom data, prioritize full-stack leadership. Revisit staffing when the bottleneck moves.

    Practical next step for staffing

    Identify the current bottleneck: unclear UX, broken implementation, or missing application logic. Hire for that bottleneck first. Reassess after two weeks of shared work. Bottlenecks move; staffing should move with them rather than freezing around the first job title you posted.

    Onboarding checklist for any hire

    Share brand assets, analytics access, staging credentials, and the definition of done for the first milestone on day one. Ambiguous onboarding creates idle senior hours. Clear onboarding is a cost control across all three roles.

    Single accountable lead

    Even with multiple crafts, name one person accountable for timeline and quality. Split ownership without a lead creates polite deadlock. Ask for that name in the proposal.

    Frequently Asked Questions

    Can one person do all three?

    Sometimes on small projects. Risk rises as design polish, integrations, and deadlines collide.

    Is a full-stack developer also a designer?

    Not always. Many strong full-stack engineers still need a designer for UX quality.

    What should be in the first call?

    Goals, examples, integrations, editors, timeline, and success metrics.

    Do we need SEO as a separate hire?

    Launch SEO hygiene can sit with the build team. Ongoing SEO programs may need dedicated specialists via technical SEO plus content owners.

  • How to Choose the Right WordPress Developer

    In short: How to choose a WordPress developer starts with clear answers on scope boundaries, staging, ownership of code and accounts, plugin policy, redirect handling, and who maintains the site after launch. Strong answers are specific. Vague portfolio talk leaves risk unexamined.

    Use this list whether you hire a freelancer or an agency like Eco Digital for WordPress development.

    Scope and discovery

    1. What is in the first milestone, and what is explicitly out?
    2. How do you handle new requests mid-project?
    3. Who writes content, and what happens if copy is late?
    4. Will we get a written sitemap and template list?

    Technical practice

    1. Do you build on staging before production?
    2. How do you take backups before major changes?
    3. What is your plugin selection policy?
    4. How do you test forms and key conversions after updates?

    SEO and URLs

    1. Who owns titles, meta, and redirects if URLs change?
    2. Will you deliver a redirect map for migrations?
    3. How do you avoid shipping staging noindex to production?

    Permanent moves should use permanent redirects (Google documentation).

    Ownership and handoff

    1. Who owns the theme, custom code, and repo?
    2. Which accounts will be in our email address at handoff?
    3. How is editor training delivered?

    Care after launch

    1. What does monthly care include and exclude?
    2. How are emergencies billed?

    Pair build with website maintenance when you lack in-house WordPress ops.

    Red flags

    • No staging
    • Unlimited revisions without definition
    • “SEO guaranteed”
    • Client does not own admin access
    • No written exclusions

    How Eco Digital answers these

    We quote fixed scopes after discovery, keep backups before meaningful changes, and separate redesigns from care plans. Platform decisions stay visible through website development. Sacramento clients can review local presence details on Sacramento web development.

    Scoring proposals quickly

    Give each proposal a 1 to 5 on staging discipline, ownership clarity, SEO/redirect plan, care plan realism, and communication cadence. Average the scores before you look at price. The cheapest bid with a zero on ownership is usually the most expensive recovery project.

    Portfolio evaluation beyond homepage screenshots

    Ask for a staging walkthrough of forms, mobile nav, and the CMS editor. Screenshots hide slow templates and brittle builders. A twenty-minute shared session reveals more than a PDF deck. Pay for that evaluation time if needed; it is cheaper than hiring the wrong partner.

    Field notes on vendor selection

    Score staging discipline, ownership clarity, redirect plans, and care realism before chemistry calls. Paid narrow trials beat free speculative work. Milestone payment schedules keep use when staging quality slips.

    Contract clauses worth reading twice

    Look for unlimited liability surprises, vague IP assignment, automatic renewal of care plans, and “time and materials” language hiding inside a fixed-bid summary. Ask what happens if a third-party plugin is abandoned mid-project. Ask how security incidents are billed.

    A clean contract will not make a weak developer strong, but a vague contract can make a strong project painful. Align the SOW, the timeline, and the payment schedule so incentives encourage staging discipline and documentation, not only speed.

    Sample message you can send vendors

    Subject: WordPress project discovery questions

    Please answer: staging and backup practice; plugin policy; who owns redirects on URL changes; who owns theme/code/accounts at handoff; what monthly care includes and excludes; and three staging URLs we can click through. We will compare answers before scheduling a creative presentation.

    That email filters marketing theater quickly. Vendors who cannot answer in writing rarely gain clarity mid-build.

    References and proof to request

    Ask for two contacts from projects similar in size, plus a staging walkthrough of forms and the editor. If the vendor only shows homepage screenshots, you have not validated mobile templates or CMS usability. Pay for a short paid discovery if needed; it is cheaper than a mismatched hire.

    Practical next step for hiring

    Send the question list to two or three vendors the same day. Score answers within 48 hours using staging discipline, ownership clarity, redirect plan, and care realism. Schedule walkthroughs only with the top scorers. This keeps hiring momentum without sliding into endless chemistry calls that never test delivery habits.

    Payment schedule that encourages quality

    Tie payments to milestones: discovery complete, design approved, staging acceptance, launch, and documentation handoff. Avoid large upfront percentages that reduce use when staging quality is weak.

    After you sign

    Schedule the access checklist on day one: staging, analytics, Search Console, brand files, and plugin licenses. Put the redirect owner and content owner on the kickoff invite. Early clarity prevents idle senior hours while someone hunts passwords.

    Frequently Asked Questions

    Should I hire a freelancer or an agency?

    Freelancers can excel on contained builds. Agencies help when you need design, development, and care coordination under one SOW.

    Do I need a designer and a developer?

    For custom visuals, yes, or a team that covers both. Template builds may need less design time.

    What is a fair trial task?

    A paid, narrow task with a clear brief beats free speculative work.

    When is WordPress the wrong hire?

    When the product needs a full-stack application. See full-stack development.

  • Why Is My Website Not Ranking on Google?

    In short: Why is my website not ranking on google? It usually traces to one of five buckets: the URL is not indexed, the page targets the wrong intent, the content is thin or duplicated, technical barriers block crawling or usability, or the site lacks enough trust relative to competitors. Fix the bucket you are in before rewriting everything.

    This diagnostic is the same order Eco Digital uses before scoping SEO services or technical SEO implementation on WordPress and related stacks.

    First split: not indexed versus indexed but low

    Search Google for site:yourdomain.com/your-page. If nothing returns, you may have an indexing problem. Confirm with URL Inspection in Search Console. If the page is indexed but ranks on page five for your target phrase, you have a relevance, quality, or competition problem instead.

    Mixing those two problems wastes weeks. Indexing first. Ranking quality second.

    Indexing and crawl blockers

    Common blockers:

    • noindex left on from staging
    • Robots.txt disallowing important paths
    • Soft 404 templates that look empty to Google
    • Canonical tags pointing at a different URL
    • Server errors or intermittent downtime
    • Orphan pages with no internal links

    Google’s Search Essentials outline technical requirements for eligibility. Meeting them does not guarantee a top rank; failing them can keep you invisible.

    After a website redesign, missing redirects are a frequent cause of sudden ranking loss. Map old URLs to new ones with permanent redirects (Google on 301 redirects).

    Query and intent mismatch

    Your homepage might be indexed yet fail for “emergency plumber pricing” if it only shows brand storytelling. Align title, H1, first paragraph, and page type with what already ranks. If the top results are calculators or pricing tables, a vague About page will not displace them.

    Build supporting insights that feed service pages from website development and WordPress development when the CMS needs structural help.

    Thin, duplicated, or doorway content

    Copy spun across dozens of city URLs without unique value is a classic failure mode. Eco Digital serves customers nationwide remotely and only claims a physical presence in Sacramento (Sacramento web development). City pages must still earn uniqueness with industries, FAQs, and proof.

    Duplicate title tags, thin tag archives, and near-identical service blurbs also dilute relevance.

    Technical and experience problems

    Slow mobile templates, intrusive interstitials, broken forms, and heavy scripts can undermine pages that are otherwise on-topic. Core Web Vitals are not the only factor, but users bounce from painful pages, and that behavior does not help.

    Plugin conflicts on WordPress that emit duplicate schema or conflicting canonicals belong in this bucket too.

    Trust, links, and brand signals

    If competitors earn mentions from relevant sites and you earn none, catching up takes deliberate digital PR and partnerships. Fake link schemes create cleanup risk under Google’s spam policies. Prefer relevant, earned references.

    Author and organization clarity on the site also helps readers trust you. Use real team names when bylines go live.

    Local packing problems

    For local queries, Google Business Profile categories, service areas, reviews, and NAP consistency matter. If the profile is unverified, category-mismatched, or shows the wrong service area, map pack visibility suffers even when the website is decent.

    A practical diagnostic order

    1. URL Inspection and site: checks for money URLs
    2. Robots, canonical, and redirect audit
    3. Title/H1/intent match versus the live SERP
    4. Content uniqueness and internal linking
    5. Speed and mobile usability on key templates
    6. Local profile accuracy if local intent matters
    7. Competitor gap on links and content depth

    Document findings before changing ten things at once.

    When to bring in help

    Bring implementation help when the diagnosis is clear but shipping capacity is not: crawl fixes, template changes, redirect maps, or content refreshes that marketing cannot push alone. Eco Digital implements on-site work rather than leaving a static audit PDF.

    Explore Our SEO Services

    Want a ranked diagnosis with fixes shipped on your site?

    Explore Our SEO Services

    Migration-specific ranking drops

    If rankings fell right after a redesign, inspect redirects, canonicals, and title changes before rewriting content. A missing redirect from a powerful old URL to its new equivalent can look like “Google tanked us” when the traffic points at a 404.

    Compare a pre-launch crawl to a post-launch crawl. Diff titles and status codes. That mechanical work recovers more migrations than panic blogging.

    Content quality issues that look technical

    Sometimes the site is indexed and healthy, yet pages rank poorly because they repeat marketing slogans without answering the query. Compare your top page to the top three results and list subtopics they cover that you skip. Fill those gaps with experience you have. If you lack experience on a topic, do not publish filler; narrow the query.

    A note on patience versus denial

    After you fix clear blockers, give Google time to recrawl before declaring failure. Checking rankings hourly creates false drama. Equally, waiting six months with no shipped changes is neglect, not patience. Balance shipping cadence with measurement windows measured in weeks.

    Frequently Asked Questions

    How do I check if Google indexed my page?

    Use site:URL as a quick hint and URL Inspection in Search Console as the authoritative check. Request indexing only after fixing blockers.

    Does a new site always struggle?

    New sites often need more time to earn trust and gather useful pages. That is different from being blocked from the index entirely.

    Can a penalty explain zero rankings?

    Manual actions appear in Search Console when present. Most “not ranking” cases are quality, intent, or indexing issues rather than a dramatic penalty.

    Will switching SEO plugins fix rankings?

    Rarely by itself. Plugins help manage titles and sitemaps. Switching without a migration plan can even create regressions. Fix content and technical causes first.

  • SEO vs Google Ads: Which Is Better for Your Business?

    In short: SEO vs Google Ads is a budget and timing decision. Ads buy visibility quickly while you pay per click or impression. SEO builds durable organic presence that compounds when pages, technical health, and trust improve. Many growing businesses use both: ads for immediate demand, SEO for lower long-run acquisition cost on the queries that matter.

    If you are choosing where to invest after launching website development work, this breakdown helps you pick a primary path and a supporting one. Eco Digital’s hands-on work sits in SEO services implemented on your site.

    Quick comparison table

    Dimension Google Ads SEO
    Speed Can show traffic as soon as campaigns are approved and funded Usually measured in months for meaningful organic gains
    Cost shape Ongoing media spend; stops when budget stops Investment in pages, technical work, and content that can keep working
    Control Bid, copy, and landing page tests are direct You control the site; you do not control Google’s ranking algorithm
    Best for Fast tests, competitive terms, time-bound offers Sustainable demand capture on service and research queries
    Main risk Rising CPCs, weak landing pages, wasted spend Slow feedback loop, underfunded implementation, thin content

    What Google Ads is good at

    Paid search shines when you need leads this month, want to test messaging, or must appear for expensive terms while organic catches up. You can pause, raise budgets, and swap landing pages quickly. That agility is hard to match with organic alone.

    Ads also expose which keywords convert before you invest months building organic pages for the wrong intent.

    What SEO is good at

    SEO improves the unpaid results people click when they research and compare. Strong organic pages keep working after the campaign budget pauses. For service businesses, organic often captures “how,” “how much,” and “best” research that later becomes a quote request.

    SEO also reinforces brand queries and supports local visibility when NAP and Google Business Profile are consistent. For Eco Digital, that local presence is Sacramento through Sacramento web development; other cities are served remotely.

    Cost shape: media spend versus asset building

    Ads bill for attention. When spend stops, most of that traffic stops. SEO spend goes into assets: clearer service pages, better crawl paths, useful guides, and cleaner WordPress templates via WordPress development when the CMS needs work.

    Neither path is free. SEO without implementation labor stalls. Ads without conversion-ready pages burn cash.

    Speed to first leads

    If payroll depends on inquiries next week, ads (or outbound) usually win the sprint. SEO wins more of the marathon when your site already ranks for something and you improve from there. New domains should expect a longer organic ramp.

    Control and risk

    With ads you control budgets and creatives, subject to Google’s ad policies. With SEO you control your site and reputation signals, subject to Search quality systems. Neither channel is “set and forget.” Google documents that appearing in Search does not require payment for organic listings (Search Essentials), while ads remain a separate sponsored product.

    When SEO is the better primary bet

    • You can fund three to twelve months of steady implementation
    • Your offer converts when the right people arrive
    • Competitors’ organic pages are beatable on specificity and usefulness
    • You want compounding visibility on educational queries that feed SEO services and development leads

    When ads should lead

    • You need pipeline immediately
    • You are validating a new service before publishing a large content set
    • Organic competition is dominated by national brands you cannot out-resource yet
    • Seasonal campaigns need precise on/off timing

    Using both without double-counting success

    Attribute carefully. A prospect might click an ad once and later convert on an organic blog post. Use analytics with realistic lookback and labeled landing pages. Let ads cover gaps while SEO pages mature, then shift budget as organic share grows on converting terms.

    How Eco Digital fits this decision

    We build sites and implement technical and on-page SEO. We do not claim secret ranking switches. If you already run ads with another partner, we make sure landing pages, titles, and crawl health support both channels.

    Explore Our SEO Services

    Ready to grow organic traffic with work shipped on your site?

    Explore Our SEO Services

    Budget scenarios for small teams

    Tight cash, need leads this month: put most of a modest budget into tightly themed ads landing on a clear service page, while funding a smaller SEO foundation (indexing, titles, one or two priority pages).

    Stable cash, brand already gets some organic traffic: invest more in SEO implementation and content, and keep ads on the highest-converting terms only.

    Launching a new service: use ads to test messaging quickly, then lock winning language into organic service pages and insights.

    These are planning patterns, not universal formulas. Your margins and sales cycle change the mix.

    Landing page quality is the shared constraint

    Whether the click is paid or organic, a vague homepage wastes it. Strengthen offers, proof, and forms through website development so both channels benefit. SEO versus ads debates often mask a conversion-rate problem.

    Frequently Asked Questions

    Is SEO free?

    No. Tools can be free, but skilled work, content, and development time are not. Organic clicks are unpaid; earning them still costs effort.

    Can I rank without ads?

    Yes. Most organic results are unpaid. Ads can help while you build, but they are not required for organic eligibility.

    Will ads hurt my organic rankings?

    Google has stated that buying ads does not improve organic rankings by itself. Separate systems power ads and organic results. Weak landing pages hurt both channels’ conversion rates.

    Which should a new website start with?

    Many new sites use a modest ad budget for immediate learning and a parallel SEO foundation: indexing, core service pages, and a short list of research articles. Exact split depends on cash flow and competition.

  • Website Redesign SEO Checklist

    This website redesign SEO checklist is the launch-side list we use so a new design does not wipe the rankings you already have.

    In short: To redesign without losing SEO, inventory every indexable URL, map each one to a new destination, launch with permanent server-side redirects for moved pages, keep valuable content and metadata, and verify coverage in Search Console after go-live. Skipping the redirect map is the most common self-inflicted ranking drop.

    Design teams ship beautiful rebuilds. Rankings fall when URLs change quietly. This checklist is the process we use on website redesign projects and the same pattern we document for consolidating domains. It is intentionally practical, so a non-SEO teammate can run the list before launch.

    Why redesigns hurt SEO (when they do)

    Common failure modes:

    • Old URLs 404 with no 301/308
    • Redirect chains (A → B → C) and loops
    • Thin replacement pages that drop unique content
    • Canonical tags pointing at the wrong host
    • Sitemap still listing retired URLs
    • Soft 404s that return 200 with “page not found” copy
    • Blocked staging robots rules copied to production

    Google treats permanent server-side redirects as a signal that the new URL should be canonical (Redirects and Google Search). Temporary redirects do a different job. Pick on purpose.

    Phase 0, Freeze assumptions

    Before design lock:

    1. Decide whether the domain stays the same.
    2. Decide whether URL patterns can change (/services/x/ vs /what-we-do/x/).
    3. List must-keep landing pages (money pages first).
    4. Confirm who owns DNS, hosting, and Search Console.

    If the domain changes (for example consolidating a secondary domain onto the primary), treat it as a migration plus redesign. Eco Digital’s own planned consolidation of ecodigitalagency.com onto ecodigital.agency follows the same redirect discipline: plan first, execute after backup and approval.

    Phase 1 : Crawl and inventory the old site

    Export:

    • HTML pages that return 200
    • Indexed URLs from Search Console (if available)
    • Top landing pages by clicks/impressions
    • External backlinks pointing at specific URLs (from whatever backlink source you have)
    • PDF and other linked assets you still need

    Store the inventory in a sheet with columns: old_url, status_code, title, indexable, notes.

    Phase 2 : Build the URL map

    For every old URL, choose one:

    Decision Action
    Keep Same path on the new site (ideal when possible)
    Move New path + permanent redirect
    Merge Several old URLs → one stronger page + redirects
    Kill 410 or redirect to the closest relevant parent

    Rules of thumb:

    • Money pages and pages with backlinks almost never “kill” without a destination.
    • Do not many-to-one redirect unrelated topics onto the homepage as a lazy default.
    • Prefer one-hop redirects (old → final), not chains.

    Phase 3 : Content and metadata parity

    For each kept or moved URL, check:

    • Primary topic still answered on the new page
    • Title and H1 still match intent (can be improved, not emptied)
    • Unique body content not replaced by a two-sentence stub
    • Images with meaningful alt text where needed
    • Internal links updated to new paths

    Google’s helpful-content guidance asks whether a page offers substantial, original value: not whether it is newly designed (people-first content).

    Phase 4 : Technical launch checklist

    Redirects

    • ☐ Permanent redirects for moved URLs (301 or 308)
    • ☐ No redirect chains longer than one hop where avoidable
    • ☐ HTTP → HTTPS and non-www ↔ www rules consistent with the canonical host
    • ☐ Old sitemap URLs either redirected or removed

    Indexation controls

    • ☐ Production allows crawling (robots.txt not left in staging “Disallow: /”)
    • ☐ No sitewide noindex left from staging
    • ☐ Canonical tags match the preferred host and path
    • ☐ XML sitemap submitted with only live canonical URLs

    On-page and structured data

    • ☐ Unique titles and meta descriptions on key templates
    • ☐ Breadcrumbs match the visible IA
    • ☐ Article/service schema only where accurate
    • ☐ Core templates pass a sample rich-results / schema validation if you use JSON-LD

    Performance and UX

    • ☐ Key templates checked on mobile
    • ☐ Forms and CTAs work on staging and production
    • ☐ Large images compressed

    For deeper technical work beyond launch, use technical SEO services.

    Phase 5 : Post-launch verification (first 14 days)

    1. Spot-check top 50 old URLs for correct final destinations.
    2. Crawl the new site for 404s and soft 404s.
    3. Watch Search Console Coverage / Pages for spikes in “Not found” and “Redirect.”
    4. Compare branded and money-query landing pages.
    5. Fix chains and missing redirects in a daily batch, not a month later.

    Worked mini-example (pattern only)

    Old:

    • /about-us/ → new /about/
    • /web-design-services/ → new /services/website-development/
    • /blog/post-name/ → keep /insights/post-name/ (or redirect if the hub changes)

    Sheet row example:

    https://example.com/about-us/,301,https://example.com/about/,keep-content,about

    This is the same style of map we use when planning domain consolidations and redesigns for clients.

    Internal links to update on launch day

    • Header and footer nav
    • Service hub cards
    • City or location pages that point at services
    • Insight posts that cite old paths
    • PDF and email templates (as you can)

    Sacramento local pages should keep NAP and service links consistent: see Sacramento web development.

    Staging hygiene (the quiet killer)

    Before you open the firewall:

    • ☐ Staging is noindex or locked from public crawl
    • ☐ Production robots/txt is not a copy of staging disallow-all
    • ☐ Basic auth on staging does not accidentally remain as the only way to see key resources on production
    • ☐ Analytics/test pixels on staging will not pollute production reporting after clone

    Many “Google deindexed us after redesign” incidents are self-inflicted staging leaks, not mysterious algorithm events.

    Analytics and Search Console cutover

    • ☐ Confirm production property in Search Console matches the canonical host
    • ☐ Keep the old property long enough to watch sharp 404 spikes
    • ☐ Update sitemap reference in robots.txt if needed
    • ☐ Verify GA4/gtag or equivalent fires on key templates after theme change
    • ☐ Annotate the redesign launch date in your analytics tool

    Without annotations, teams argue about traffic changes with no shared timeline.

    Practical next step

    Create the URL inventory before the design team finalizes slugs. Approve the redirect map as a launch gate. After go-live, spend the first two weeks on QA, not on new landing-page ideas. If you need a crew to run the checklist, pair website redesign with technical SEO and keep Search Console open during cutover.

    Frequently Asked Questions

    Do I need redirects if I only change the design?

    If URLs stay identical, you may need few or no redirects. Still verify canonicals, sitemap, and that staging noindex did not ship.

    Is a 301 better than a 302 for a permanent redesign URL change?

    For permanent moves, Google documents permanent redirects (including 301 and 308) as the signal that the new URL should be canonical. Use temporary redirects when the change is not permanent.

    How long do redirects need to stay in place?

    Plan for the long term. Remove redirects only when you are sure no meaningful traffic or links hit the old URLs: and even then, prefer caution on URLs with backlinks.

    Can I redesign and change domains at the same time?

    Yes, but risk stacks. Complete a careful URL map, keep content parity, and monitor Search Console closely. Sequence work if the team is small.

    Who should own the checklist: designer or developer?

    Both. Design owns content parity and templates; engineering owns redirects, headers, sitemap, and robots. SEO reviews the map before launch.

  • How Long Does SEO Take to Show Results?

    In short: How long does SEO take to show results? It depends on competition, site history, and how quickly changes go live, but many businesses should plan for months rather than days. Technical and on-page fixes can show early coverage or query movement first. Stable traffic and lead growth usually take longer, especially on new domains or competitive terms.

    Owners ask this before signing an SEO retainer because cash flow matters. Eco Digital scopes SEO services with milestones you can inspect in Search Console, not with guaranteed rankings.

    A plain answer before the nuance

    If your site can already be crawled, a focused round of fixes and content can produce visible query or landing-page changes within several weeks for easier terms. Competitive head terms and brand-new domains often need a longer runway. Treat “overnight first page” offers as a red flag.

    What Google has said about timing

    Google’s documentation explains that changes can take anywhere from hours to months to reflect, and that not every change creates a noticeable ranking impact (SEO starter guide). In a widely cited Google webmaster video, Maile Ohye described a common range of roughly four months to a year for SEO work to be implemented and for potential benefit to appear. That is a planning range, not a promise for every site.

    Factors that speed up or slow down results

    Site history and authority. Established sites with clean link profiles and useful pages often move faster than brand-new domains.

    Competition. Ranking for a niche service phrase in a mid-size market is different from ranking for a national generic term.

    Implementation speed. Recommendations sitting in a slide deck do nothing. Developer capacity and content production pace control the clock. Pairing SEO with capable WordPress development shortens that lag.

    Technical debt. Index bloat, broken templates, or a messy website redesign without redirects can erase gains.

    Local versus broad intent. Local queries tied to a real presence (for Eco Digital, Sacramento via Sacramento web development) can move differently from nationwide informational queries.

    Month-by-month expectations for a small business site

    Use this as a planning sketch, not a contract:

    • Month 1: Audit, analytics and Search Console validation, keyword map, priority list. Few public ranking fireworks.
    • Months 2-3: Ship technical fixes, improve money templates, publish or refresh priority pages.
    • Months 3-6: Watch impressions, positions for target clusters, and early organic conversions. Rankings may bounce while Google reevaluates.
    • Months 6-12: Compounding on content and authority work for harder terms, if the foundation held.

    Your calendar will differ. A site with severe crawl blocks may need longer on fundamentals before content investment pays.

    Early signals versus revenue impact

    Early signals include better index coverage, rising impressions, and pages moving from the teens into the top ten for mid-difficulty phrases. Revenue impact needs enough qualified clicks plus a site that converts. If rankings rise but leads do not, inspect offer clarity, forms, and speed before blaming SEO alone.

    When “no results” means a real problem

    Investigate if, after a fair window with shipped work:

    • Money URLs are still excluded from the index
    • Impressions stay near zero for targeted queries
    • The site was hit by a manual action or clear spam issue
    • Competitors with thinner pages still dominate while your titles and content miss intent

    Those are diagnostic problems, not reasons to buy a miracle package.

    How to set milestones with your SEO partner

    Ask for:

    1. A written list of pages and queries in scope
    2. Shipping dates for technical and content items
    3. Search Console metrics you will review together
    4. What is out of scope (for example, buying links)

    Refuse vague “we will get you to page one” language. Prefer “we will implement X and measure Y.”

    How Eco Digital scopes SEO timelines

    We separate technical implementation on technical SEO from content and IA work, attach dates, and report against Search Console. Sacramento local details stay accurate; other US cities are served remotely without fake offices.

    Explore Our SEO Services

    Want a scoped plan with milestones you can verify?

    Explore Our SEO Services

    What “results” should mean in your contract

    Define results before you start. Possible definitions include index coverage for priority URLs, growth in impressions for a named cluster, a target number of organic quote forms, or improved average position for a short keyword list. If the contract only says “better SEO,” disputes are almost guaranteed.

    Separate leading indicators (coverage, impressions, click-through rate on rewritten titles) from lagging indicators (qualified leads and revenue). Leading indicators can move first. Lagging indicators need enough traffic and a site that converts.

    Communication cadence that keeps projects accountable

    Biweekly shipping notes beat monthly slide decks that hide idle weeks. Each note should list URLs changed, queries watched, and blockers waiting on the client. When development tickets sit unmerged, the SEO clock pauses even if meetings continue.

    Eco Digital prefers that cadence inside SEO services so owners see work, not theater.

    Frequently Asked Questions

    Can SEO work in 30 days?

    Sometimes you will see early indexing or query shifts in a month, especially after fixing blockers. Expecting full competitive dominance in 30 days is usually unrealistic.

    Does a new website take longer?

    Often yes. New domains need time to earn trust and gather useful content. Migrations add redirect and recrawl time on top.

    Is local SEO faster than national SEO?

    It can be when the business has a real local presence and the queries are less contested. It is still not instant, and fake locations create risk.

    Should I pause ads while SEO ramps?

    Not necessarily. Many teams keep ads on converting terms while organic catches up, then adjust budgets as organic share grows.

  • Redirect Map Builder (Free Google Sheet Tool)

    In short: A redirect map builder is a structured spreadsheet that lists every old URL, a keep/move/merge/kill decision, the new URL, redirect type, and QA status. Use it before redesigns or domain moves so permanent redirects ship as one-hop rules. Do this before launch, not after rankings drop.

    This insight is the tool brief for a copyable Google Sheet. The Sheet itself is a deliverable for the web team to publish alongside this page. Until the live Sheet link is attached in WordPress, use the column spec below to build your own in minutes. Related templates: redesign SOW + redirect map and the redesign SEO checklist.

    Why a Sheet beats a Slack thread

    Migrations fail in the gaps:

    • Design changes a slug and engineering never hears
    • Someone redirects everything to the homepage
    • Chains appear because three people add rules over three nights
    • QA never re-hits the top backlink URLs

    A single Sheet with owners and QA status prevents that. Google’s documentation expects permanent moves to use permanent redirects when the change is lasting (Redirects and Google Search). The Sheet is how humans implement that cleanly.

    Sheet tab plan

    1. Inventory: crawl export + Search Console URLs
    2. Map: decisions and destinations
    3. Rules : generated redirect lines for the server/plugin
    4. QA : sample checks post-launch
    5. Log : changes after launch

    Map tab columns (copy these headers)

    old_url
    source (crawl|gsc|backlink|manual)
    current_status_code
    decision (keep|move|merge|kill)
    new_url
    redirect_type (301|308|410|none)
    priority (money|content|asset|low)
    backlinks (yes|no|unknown)
    notes
    owner
    qa_status (unchecked|pass|fail)
    qa_checked_at
    

    Decision definitions

    • keep : path stays; redirect_type = none
    • move : one old URL to one new URL; 301/308
    • merge : many old URLs to one stronger URL; each row still gets its own redirect
    • kill : intentionally retired; prefer 410 when no useful destination exists, otherwise redirect to the closest relevant parent: not the homepage by default

    Formula helpers (optional)

    In Google Sheets you can add helper columns:

    • needs_redirect = IF(OR(decision="move", decision="merge"), "yes", "no")
    • path_only using a formula that strips the host for plugin imports
    • Conditional formatting: highlight qa_status=fail and empty new_url when needs_redirect=yes

    Generating server rules

    Apache Alias-style example

    Redirect 301 /old-path/ https://www.example.com/new-path/
    

    Nginx example

    location = /old-path/ { return 301 https://www.example.com/new-path/; }
    

    WordPress note

    If you manage redirects in Rank Math or another plugin, export old_url,new_url and import carefully. Still keep the Sheet as source of truth. Plugin UIs drift; Sheets get reviewed.

    QA protocol (built into the tool)

    Before launch:

    1. Filter priority=money and confirm every row has a destination or an explicit kill
    2. Spot-check backlinks=yes rows twice
    3. Resolve chains: if B already redirects to C, point A straight to C

    After launch:

    1. Sample 50 old URLs with curl or a crawler
    2. Mark qa_status
    3. Fix fails the same day

    How Eco Digital uses this on real projects

    On redesigns and planned domain consolidations (including our own ecodigitalagency.com → ecodigital.agency plan), the Sheet is a launch gate: no map approval, no cutover. That pairs with website redesign services and technical SEO.

    We also link money-page destinations to the new IA: often the website development pillar and local Sacramento page: so redirects land on living URLs, not placeholders.

    Publishing the live Google Sheet

    When this page goes live on WordPress:

    1. Create a Google Sheet from the columns above
    2. File → Share → anyone with link can view
    3. Optionally File → Make a copy instructions at the top row
    4. Paste the link in a callout near the top of this article
    5. Add the Sheet to the insights hub card for this tool

    Until that link exists, this page remains the specification (still useful, still indexable).

    Tool vs article: why this is experimental in the calendar

    The content calendar tags this as experimental because link earning may favor a usable Sheet over another essay. Measure:

    • Copy events / Sheet opens (if analytics allow)
    • Referring links to this URL
    • Assisted conversions from migration leads

    If the Sheet outperforms, build more tools. If not, keep the checklist posts.

    Common mistakes the Sheet prevents

    1. Homepage dumping : sending unrelated legacy URLs to / destroys relevance signals and frustrates users.
    2. Unowned rows : if owner is blank, nobody fixes QA fails.
    3. Hidden PDFs and vanity URLs : marketing links in emails and decks still get traffic; put them in Inventory with source=manual.
    4. Case and trailing-slash mismatches : normalize paths before launch or you will “fix” redirects that already exist under a different spelling.
    5. Forgetting non-HTML assets : PDFs and old image URLs linked from partners deserve decisions too.

    Minimal viable map for a five-page site

    Even small sites benefit:

    old_url decision new_url
    / keep /
    /about-us/ move /about/
    /contact-us/ move /contact/
    /services/ keep /services/
    /blog/welcome/ move /insights/welcome/

    If this feels too small for a Sheet, you still want the decisions written somewhere durable.

    Import checklist for WordPress plugins

    When moving rows into Rank Math or similar:

    • ☐ Deduplicate old paths
    • ☐ Ensure new URLs are absolute or correctly rooted per plugin rules
    • ☐ Avoid importing keep rows as redirects-to-self loops
    • ☐ Test a 5-row pilot import before the full load
    • ☐ Export a backup of existing redirect rules first

    The Sheet remains canonical even after import.

    Measuring whether the tool worked

    After launch, track:

    • Count of 404s in Search Console referring to old paths
    • Number of redirect rules still unused after 60 days (candidates to revisit)
    • Support tickets titled “old link broken”
    • Time-to-fix for the first week’s QA fails

    If 404s stay noisy, the Inventory tab was incomplete. Incomplete inventories cause noisy 404s.

    Practical next step

    1. Duplicate the column headers into a new Google Sheet today.
    2. Paste your crawl export into Inventory.
    3. Mark money pages and backlink URLs first: do not start with low-priority blog tags.
    4. Schedule a 30-minute review with whoever owns the redesign so decisions are shared.
    5. If you need Eco Digital to run the migration end-to-end, bring the Sheet to a website redesign kickoff; we will refuse launch without map approval.

    Frequently Asked Questions

    Is this really free?

    Yes: the pattern is free to copy. Agency implementation time is separate if you hire us to run the migration.

    Will you host my redirect map?

    For clients, yes, inside the project workspace. For the public tool, use “Make a copy” so your URLs stay private.

    What redirect status code should I use?

    For permanent moves, 301 or 308. Use temporary codes only for temporary situations. Use 410 for deliberate removals when appropriate.

    Can this work for Wix or Shopify moves?

    Yes. The Sheet is platform-agnostic. The export format for rules changes by host.

    Does a redirect map replace good content?

    No. It preserves pathways. Content quality still has to deserve the ranking (Google helpful content guidance).