<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Eight One Digital</title>
	<atom:link href="https://81.digital/feed/" rel="self" type="application/rss+xml" />
	<link>https://81.digital/</link>
	<description></description>
	<lastBuildDate>Sun, 01 Nov 2026 13:20:24 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.4</generator>

<image>
	<url>https://81.digital/wp-content/uploads/2026/10/site-icon-81-150x150.png</url>
	<title>Eight One Digital</title>
	<link>https://81.digital/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Do I Need a Bilingual Website in Wales?</title>
		<link>https://81.digital/blog/bilingual-website-wales/</link>
		
		<dc:creator><![CDATA[Hywel]]></dc:creator>
		<pubDate>Wed, 18 Nov 2026 09:00:36 +0000</pubDate>
				<category><![CDATA[Guides]]></category>
		<category><![CDATA[Bilingual Websites]]></category>
		<category><![CDATA[Charities]]></category>
		<category><![CDATA[Public Sector]]></category>
		<category><![CDATA[Wales]]></category>
		<category><![CDATA[Welsh Language]]></category>
		<guid isPermaLink="false">https://81.digital/?p=146351</guid>

					<description><![CDATA[<p>Public bodies in Wales with Welsh language standards usually need a fully bilingual website. Most businesses and charities do not, but there is free help if you want to add Welsh. Here is where the line falls and how to do it properly.</p>
<p>The post <a href="https://81.digital/blog/bilingual-website-wales/">Do I Need a Bilingual Website in Wales?</a> appeared first on <a href="https://81.digital">Eight One Digital</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>It depends on who you are. If your organisation is a public body in Wales that has been given a compliance notice under the Welsh language standards, your website almost certainly has to be fully bilingual, and the Welsh version cannot be treated less favourably than the English one. If you are a private business or most kinds of charity, there is no general legal requirement for a bilingual website, but there are good reasons to offer some Welsh, and free help to do it. This guide explains where the line falls and how I would approach a bilingual website in practice.</p>
<h2>Who has to provide Welsh on their website?</h2>
<p>The Welsh Language (Wales) Measure 2011 gave Welsh official status in Wales and created the Welsh language standards. Only organisations named in the Measure, or that fall into one of its listed categories, can be required to follow standards. In practice that means most public organisations in Wales, such as councils, health boards, national park authorities, universities and colleges, along with some UK-wide bodies that provide public services in Wales.</p>
<p>Each organisation receives a compliance notice from the Welsh Language Commissioner listing exactly which standards it must meet and from when. Some organisations are still working to a Welsh language scheme under the older Welsh Language Act 1993 instead. Either way, the starting point is to check your own compliance notice or scheme, because that is what you will be measured against.</p>
<h3>What the website standards say</h3>
<p>The website standards are set out in the <a href="https://www.legislation.gov.uk/wsi/2015/996/schedule/1" target="_blank" rel="noreferrer noopener">Welsh Language Standards (No. 1) Regulations 2015</a>. If they appear in your compliance notice, they cover things like:</p>
<ul>
<li>making the text of every page on your website available in Welsh, with each Welsh page fully functional</li>
<li>making the homepage available in Welsh</li>
<li>providing Welsh text whenever you publish a new page or amend an existing one</li>
<li>stating clearly on each English page that it is also available in Welsh, with a link to the Welsh page</li>
<li>providing the interface and menus on every page in Welsh</li>
<li>making sure any apps you publish work fully in Welsh</li>
</ul>
<p>Not every organisation has every standard, so the wording in your own notice matters. The point to take from the list is that a Welsh homepage with English pages behind it is not enough for most public bodies.</p>
<h2>What about charities and small businesses?</h2>
<p>Most charities, community groups and private businesses are not subject to the Welsh language standards, so there is no general legal duty to have a bilingual website. That can change if you deliver a public service under contract or receive funding with Welsh language conditions attached, so it is worth reading the terms of any grant or contract carefully.</p>
<p>Even where it is optional, I think a sensible amount of Welsh is worth considering, particularly if your customers or service users are Welsh speakers or you work with public bodies that are. The Welsh Language Commissioner runs a scheme called the Cynnig Cymraeg (Welsh Offer) that recognises businesses and charities with a strong plan for their Welsh language services.</p>
<h3>Free translation help</h3>
<p>The Welsh Government&#8217;s <a href="https://businesswales.gov.wales/heloblod/helo-blod" target="_blank" rel="noreferrer noopener">Helo Blod service</a> offers free Welsh translation for businesses, charities and community groups, up to 500 words a month, along with free checking of Welsh text you have written yourself. That is not enough to translate a large website in one go, but it is useful for a homepage, key service pages, contact details or signage, and you can build up over time.</p>
<h2>How to build a bilingual website properly</h2>
<p>Whether you are required to or not, a bilingual site works best when it is planned from the start rather than added later. These are the things I look at.</p>
<h3>Give each language its own pages</h3>
<p>Each page should exist as a separate Welsh page and English page, with its own address, rather than both languages crammed side by side or swapped in by a script. On WordPress this is normally handled with a multilingual plugin that links each page to its translation. Separate pages are easier for visitors to read, easier to keep up to date and easier for search engines to understand.</p>
<h3>Make the language switch obvious</h3>
<p>Put a clear link to the other language in the same place on every page, usually in the header, and make it go to the equivalent page rather than back to the homepage. Someone reading about your opening hours in English should land on the Welsh opening hours page when they switch.</p>
<h3>Translate the whole interface</h3>
<p>Menus, buttons, form labels, error messages, cookie banners and footer text are easy to forget. If they stay in English, the Welsh site feels unfinished, and for organisations under the standards it may not comply.</p>
<h3>Tell search engines about both versions</h3>
<p>Google recommends using hreflang annotations so it knows which pages are alternate language versions of each other. According to <a href="https://developers.google.com/search/docs/specialty/international/localized-versions" target="_blank" rel="noreferrer noopener">Google&#8217;s guidance on localised versions</a>, each version should list itself and all the others, and the links must go both ways or they may be ignored. Google also says it does not use hreflang or the HTML lang attribute to work out what language a page is in, so the page content itself needs to actually be in that language.</p>
<h3>Remember accessibility</h3>
<p>Both language versions are part of your website, so if you are covered by the accessibility regulations, both need to meet the same standard. I covered that in more detail in <a href="https://81.digital/blog/charity-website-accessibility-regulations/">do charity and public sector websites have to meet accessibility regulations</a>. Setting the correct language on each page also helps screen readers pronounce the text properly.</p>
<h3>Plan for upkeep</h3>
<p>The most common problem I see on bilingual sites is not the build but what happens afterwards: an English page gets updated and the Welsh one does not. Agree who handles translation, how long it takes and who publishes it before the site goes live.</p>
<h2>Frequently asked questions</h2>
<h3>Can I use automatic translation for the Welsh version?</h3>
<p>There is no rule against machine translation tools in themselves, but I would not publish their output without a Welsh speaker checking it. Helo Blod&#8217;s free text checking is one way to do that for smaller amounts of text.</p>
<h3>Does the Welsh version have to come first?</h3>
<p>Not for most businesses and charities. For organisations under the standards, check your compliance notice, as it sets out how Welsh must be treated compared with English.</p>
<h3>Will a bilingual website hurt my SEO?</h3>
<p>Not if it is set up properly. With separate pages for each language and correct hreflang annotations, search engines can show the right version to the right person.</p>
<p>If you are planning a new bilingual site or need to bring an existing one up to standard, there is more on my <a href="https://81.digital/bilingual-accessible-websites/">bilingual and accessible websites</a> page, or you are welcome to <a href="https://81.digital/contact/">get in touch</a>.</p>
<p>The post <a href="https://81.digital/blog/bilingual-website-wales/">Do I Need a Bilingual Website in Wales?</a> appeared first on <a href="https://81.digital">Eight One Digital</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Moving From WooCommerce to Shopify: What Happens to Your Products, Customers and Orders?</title>
		<link>https://81.digital/blog/woocommerce-to-shopify-what-moves-across/</link>
		
		<dc:creator><![CDATA[Hywel]]></dc:creator>
		<pubDate>Wed, 11 Nov 2026 09:00:00 +0000</pubDate>
				<category><![CDATA[Guides]]></category>
		<guid isPermaLink="false">https://81.digital/?p=146319</guid>

					<description><![CDATA[<p>What moves across automatically, what needs extra work, and what has to be set up again when you switch from WooCommerce to Shopify.</p>
<p>The post <a href="https://81.digital/blog/woocommerce-to-shopify-what-moves-across/">Moving From WooCommerce to Shopify: What Happens to Your Products, Customers and Orders?</a> appeared first on <a href="https://81.digital">Eight One Digital</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>If you&#8217;re thinking of moving your shop from WooCommerce to Shopify, the big worry is usually what happens to everything you&#8217;ve built up: the products, the customers, the order history. Here&#8217;s what moves across, what needs a bit more work, and what has to be set up again.</p>
<p>If you&#8217;re mainly worried about Google, I&#8217;ve written a separate guide on <a href="/blog/move-to-shopify-without-losing-rankings/">moving to Shopify without losing your rankings</a>, which covers URLs and redirects.</p>
<h2>Products</h2>
<p>Products move across well. They&#8217;re exported from WooCommerce and imported into Shopify with a CSV file, including titles, descriptions, prices, SKUs, stock levels and images.</p>
<p>The part that needs care is variations. WooCommerce and Shopify handle product options differently, and Shopify has limits on how many options and variants a product can have. Products with lots of sizes, colours or finishes sometimes need restructuring, so it&#8217;s worth checking your most complicated products first.</p>
<h2>Collections and categories</h2>
<p>WooCommerce categories become Shopify collections. These are usually rebuilt rather than imported, which is a good chance to tidy up categories that have grown messy over the years.</p>
<h2>Customers</h2>
<p>Customer names, emails and addresses can be imported. Passwords can&#8217;t, because they&#8217;re stored in a way that can&#8217;t be moved between platforms. Customers with accounts will need to set a new password, and Shopify can send them an invite to do that.</p>
<h2>Orders</h2>
<p>Shopify&#8217;s built-in import doesn&#8217;t cover past orders, so order history is usually moved with a migration app. Whether it&#8217;s worth moving depends on how much you use it. Some shops bring across a few years of orders, others keep the old data exported and start fresh.</p>
<h2>Reviews</h2>
<p>Product reviews generally need a reviews app on Shopify, and most of the popular ones can import reviews from a file. It&#8217;s worth doing, because losing years of reviews is a real setback.</p>
<h2>What needs setting up again</h2>
<ul>
<li>Payment methods and checkout settings.</li>
<li>Shipping rates and delivery zones.</li>
<li>Tax settings.</li>
<li>Discount codes and gift cards.</li>
<li>Email notifications and their wording.</li>
<li>Any extra features you had through WooCommerce plugins, which may need a Shopify app or some custom work.</li>
</ul>
<h2>Plan it, then test it</h2>
<p>The smoothest moves are planned before anything is switched over: a list of what&#8217;s moving, a test of the new store with real orders, and the launch timed for a quieter period. Done that way, most customers won&#8217;t notice anything except a better shop.</p>
<h2>Thinking of moving?</h2>
<p>I move shops to Shopify with products, customers, redirects and SEO handled properly. Have a look at my <a href="/shopify-website-design/">Shopify</a> page, or <a href="/contact/">get in touch</a> to talk about your move.</p>
<p>The post <a href="https://81.digital/blog/woocommerce-to-shopify-what-moves-across/">Moving From WooCommerce to Shopify: What Happens to Your Products, Customers and Orders?</a> appeared first on <a href="https://81.digital">Eight One Digital</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>What Does WordPress Maintenance Actually Include?</title>
		<link>https://81.digital/blog/what-does-wordpress-maintenance-include/</link>
		
		<dc:creator><![CDATA[Hywel]]></dc:creator>
		<pubDate>Wed, 04 Nov 2026 09:00:00 +0000</pubDate>
				<category><![CDATA[Guides]]></category>
		<guid isPermaLink="false">https://81.digital/?p=146318</guid>

					<description><![CDATA[<p>Updates, backups, security and monitoring explained in plain English, and why websites break when nobody does them.</p>
<p>The post <a href="https://81.digital/blog/what-does-wordpress-maintenance-include/">What Does WordPress Maintenance Actually Include?</a> appeared first on <a href="https://81.digital">Eight One Digital</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>A WordPress website isn&#8217;t something you build once and forget about. It needs regular care to stay fast, secure and working, in the same way a car needs servicing. Here&#8217;s what that care actually involves, in plain English.</p>
<h2>Updates</h2>
<p>WordPress itself, your theme and every plugin get regular updates. Some add features, but many fix security holes. Leaving them for months is one of the most common reasons sites get hacked or stop working.</p>
<p>Updates shouldn&#8217;t just be clicked through blindly, though. Occasionally one plugin update clashes with another, so part of maintenance is checking the site afterwards and having a backup ready in case something needs rolling back.</p>
<h2>Backups</h2>
<p>A backup is a full copy of your website, including the files and the database that holds your pages, products and settings. Good backups run regularly, are stored away from the website&#8217;s own server, and have been tested so you know they actually restore. A backup you&#8217;ve never tested is only a hope.</p>
<h2>Security</h2>
<p>This covers keeping SSL certificates valid (the padlock in the browser), removing old user accounts, using strong passwords, and watching for anything suspicious. Most attacks on small business websites aren&#8217;t personal. They&#8217;re automated, and they look for sites running old software.</p>
<h2>Monitoring</h2>
<p>Monitoring means something checks your website regularly and raises an alert if it goes down. Without it, the first you hear of a problem is often a customer telling you, which might be days later.</p>
<h2>Fixes and small changes</h2>
<p>Forms stop sending, layouts break on a new phone, a plugin is discontinued. Good maintenance includes sorting these out, and usually covers small content changes too, like updating text, swapping images or adding a new page.</p>
<h2>Why sites break when nobody does this</h2>
<p>Most of the broken websites I&#8217;m asked to look at weren&#8217;t badly built. They just weren&#8217;t looked after. A few years of missed updates can turn a simple job into a much bigger one, which is why a little regular care is usually cheaper than an emergency fix.</p>
<h2>Want it taken care of?</h2>
<p>I look after more than 40 client websites. See my <a href="/website-support-services/">Website Support</a> page for ongoing care, or <a href="/managed-website-hosting/">Managed Website Hosting</a> if you&#8217;d like the hosting and maintenance handled in one place. You can also <a href="/contact/">get in touch</a> to talk it through.</p>
<p>The post <a href="https://81.digital/blog/what-does-wordpress-maintenance-include/">What Does WordPress Maintenance Actually Include?</a> appeared first on <a href="https://81.digital">Eight One Digital</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Can Someone Take Over My Existing WordPress Website?</title>
		<link>https://81.digital/blog/can-someone-take-over-my-wordpress-website/</link>
		
		<dc:creator><![CDATA[Hywel]]></dc:creator>
		<pubDate>Wed, 28 Oct 2026 09:00:00 +0000</pubDate>
				<category><![CDATA[Guides]]></category>
		<guid isPermaLink="false">https://81.digital/?p=146317</guid>

					<description><![CDATA[<p>Your web designer has gone quiet, retired or moved on. Here's how a website takeover works and what you'll need to hand over.</p>
<p>The post <a href="https://81.digital/blog/can-someone-take-over-my-wordpress-website/">Can Someone Take Over My Existing WordPress Website?</a> appeared first on <a href="https://81.digital">Eight One Digital</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>It happens more often than you&#8217;d think. The person who built your website has stopped replying, retired, or moved on to something else, and you&#8217;re left with a site nobody is looking after. The good news is that a WordPress website can almost always be taken over by someone new, whoever built it.</p>
<h2>Yes, it&#8217;s normal</h2>
<p>WordPress is used by a huge number of websites, so it isn&#8217;t tied to the person who set it up. As long as you can get access, another developer can pick it up, check it over and carry on looking after it. I regularly take on sites built by other designers and agencies.</p>
<h2>What you&#8217;ll need</h2>
<p>To take over a website properly, these are the logins that matter:</p>
<ul>
<li><strong>The WordPress admin login</strong>, ideally an administrator account in your own name.</li>
<li><strong>Your hosting account</strong>, where the website files and database live.</li>
<li><strong>Your domain registrar</strong>, where your web address is registered and renewed.</li>
<li><strong>Your DNS settings</strong>, which control where your domain and email point.</li>
</ul>
<p>Don&#8217;t worry if you don&#8217;t have them all. It&#8217;s very common to find the domain or hosting was set up in the old designer&#8217;s name. In most cases access can be recovered through the hosting company or registrar, and it&#8217;s worth doing, because whoever controls the domain controls your website and email.</p>
<h2>What I check first</h2>
<p>Before changing anything, I take a full backup and do a health check, so I know exactly what I&#8217;m working with. That covers:</p>
<ul>
<li>WordPress, theme and plugin versions, and how out of date they are.</li>
<li>Which plugins are actually in use, and which can go.</li>
<li>Whether backups are running, and where they&#8217;re stored.</li>
<li>Security: user accounts, passwords and any signs of malware.</li>
<li>Speed, contact forms, and whether emails from the site are being delivered.</li>
</ul>
<h2>Common problems on neglected sites</h2>
<p>Sites that haven&#8217;t been looked after for a while tend to have the same issues: plugins years out of date, old admin accounts nobody recognises, contact forms that quietly stopped sending, expired licences for paid plugins, and no recent backup. None of these are unusual, and most can be sorted fairly quickly once they&#8217;ve been found.</p>
<h2>What happens next</h2>
<p>Once the site is safe and up to date, you can decide how you want it looked after. Some people want ongoing support with updates, backups and changes when they need them. Others want to move the whole thing onto hosting that&#8217;s managed for them, so everything is in one place.</p>
<h2>Need a hand?</h2>
<p>If your website needs a new home or someone to look after it, have a look at my <a href="/website-support-services/">Website Support</a> and <a href="/managed-website-hosting/">Managed Website Hosting</a> pages, or <a href="/contact/">get in touch</a> and tell me what&#8217;s going on.</p>
<p>The post <a href="https://81.digital/blog/can-someone-take-over-my-wordpress-website/">Can Someone Take Over My Existing WordPress Website?</a> appeared first on <a href="https://81.digital">Eight One Digital</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Do Charity and Public Sector Websites Have to Meet Accessibility Regulations?</title>
		<link>https://81.digital/blog/charity-website-accessibility-regulations/</link>
		
		<dc:creator><![CDATA[Hywel]]></dc:creator>
		<pubDate>Mon, 26 Oct 2026 12:50:24 +0000</pubDate>
				<category><![CDATA[Guides]]></category>
		<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Charities]]></category>
		<category><![CDATA[Public Sector]]></category>
		<category><![CDATA[Wales]]></category>
		<category><![CDATA[WCAG]]></category>
		<guid isPermaLink="false">https://81.digital/?p=146348</guid>

					<description><![CDATA[<p>Public sector websites in Wales must meet WCAG 2.2 AA and publish an accessibility statement. Most charities are exempt from the regulations, but not all, and the Equality Act still applies. Here is how to check where you stand.</p>
<p>The post <a href="https://81.digital/blog/charity-website-accessibility-regulations/">Do Charity and Public Sector Websites Have to Meet Accessibility Regulations?</a> appeared first on <a href="https://81.digital">Eight One Digital</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>If your organisation is a public sector body in Wales, such as a council, health board, college or another organisation that is mostly funded by public money, the answer is yes. Your website has to meet the WCAG 2.2 AA standard and publish an accessibility statement under the accessibility regulations for public sector websites. Most charities are exempt from those regulations, but not all of them are, and every organisation that provides a service still has duties under the Equality Act 2010. This guide explains how to work out where you stand and what to do next.</p>
<h2>Who the accessibility regulations cover</h2>
<p>The rules are set out in the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. According to the <a href="https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-websites-and-apps" target="_blank" rel="noreferrer noopener">government guidance on accessibility requirements</a>, they apply to central and local government organisations and to some charities and other non-government organisations. They cover public-facing websites, intranets, extranets and mobile apps developed for public use.</p>
<h3>When a charity is covered</h3>
<p>Charities and other non-government organisations are exempt unless at least one of these applies:</p>
<ul>
<li>they are mostly funded by public money</li>
<li>they provide services that are essential to the public</li>
<li>their services are aimed at disabled people</li>
</ul>
<h3>Partial exemptions</h3>
<p>Primary and secondary schools and nurseries are partly exempt. They do not have to make everything accessible, but the content people need in order to use their services must be, and they still need to publish an accessibility statement. Public sector broadcasters are fully exempt.</p>
<h2>What WCAG 2.2 AA actually asks for</h2>
<p>WCAG stands for the Web Content Accessibility Guidelines, published by the W3C. Version 2.2 became a W3C Recommendation on 5 October 2023. It keeps almost everything from version 2.1, removes one obsolete criterion (4.1.1 Parsing) and adds nine new success criteria, as listed in the <a href="https://www.w3.org/WAI/standards-guidelines/wcag/new-in-22/" target="_blank" rel="noreferrer noopener">W3C summary of what is new in WCAG 2.2</a>. Six of the new criteria are at level A or AA, so they matter for the public sector standard:</p>
<ul>
<li><strong>Focus Not Obscured (Minimum):</strong> when someone moves through the page with a keyboard, the item they are on should not be completely hidden behind a sticky header, chat widget or cookie banner.</li>
<li><strong>Dragging Movements:</strong> anything that needs dragging, such as a slider, should also work with a single tap or click.</li>
<li><strong>Target Size (Minimum):</strong> buttons and links need to be big enough, or spaced far enough apart, to be pressed easily. The guideline uses 24 by 24 CSS pixels, with some exceptions.</li>
<li><strong>Consistent Help:</strong> if you offer help, such as contact details or a help page link, it should appear in the same place across pages.</li>
<li><strong>Redundant Entry:</strong> people should not have to type the same information twice in the same process, for example on a multi-step donation or referral form.</li>
<li><strong>Accessible Authentication (Minimum):</strong> logging in should not depend on remembering or solving something, like a puzzle, unless there is an alternative.</li>
</ul>
<p>The older criteria still apply too, and in practice they are where most problems are found: missing image descriptions, poor colour contrast, unlabelled form fields, confusing heading structure and pages that cannot be used with a keyboard.</p>
<h2>The accessibility statement</h2>
<p>Organisations covered by the regulations must publish an accessibility statement on the website or app it relates to. It should explain how accessible the site is, list any content you have not fixed because it is exempt, and list anything you have decided would be a disproportionate burden to fix. If your site is run by an outside supplier, the statement should also set out the plans you have agreed for fixing remaining issues. The guidance says to review and update it regularly, so it is not a one-off job.</p>
<h2>Content you may not need to fix</h2>
<p>Some content is exempt from the regulations, including:</p>
<ul>
<li>PDFs and other documents published before 23 September 2018, unless people need them to use one of your services</li>
<li>pre-recorded audio and video published before 23 September 2020</li>
<li>live audio and video</li>
<li>maps, as long as essential information is provided in an accessible way</li>
<li>third-party content you have not paid for or developed, such as social media buttons</li>
<li>archived websites that are not needed for services and are not updated</li>
</ul>
<p>You can also claim that a particular fix would be a disproportionate burden, but this needs a proper assessment. The guidance is clear that you cannot count things like lack of time or knowledge.</p>
<h2>If your charity is exempt, does any of this matter?</h2>
<p>Yes, to a degree. The regulations build on the Equality Act 2010, and the government guidance points out that all UK service providers have a legal duty to make reasonable adjustments for disabled people. That duty still applies if you are exempt from the regulations. A common example is providing information in an accessible format when someone asks for it.</p>
<h2>Who checks and enforces this?</h2>
<p>In England, Scotland and Wales, the Equality and Human Rights Commission enforces the requirement, with powers that include investigations, unlawful act notices and court action. Separately, the Government Digital Service monitors a sample of public sector websites and apps each year.</p>
<h2>Where to start</h2>
<ol>
<li><strong>Work out whether you are covered.</strong> Use the three tests above for charities, and note any partial exemptions.</li>
<li><strong>Check the site against WCAG 2.2 AA.</strong> Automated checkers are a useful first pass but cannot test everything, so add manual checks such as moving through every page with only a keyboard.</li>
<li><strong>Fix the common issues first.</strong> Image descriptions, colour contrast, form labels, headings and keyboard access usually make the biggest difference.</li>
<li><strong>Publish or update your accessibility statement.</strong> Be honest about what still needs work and when you plan to fix it.</li>
<li><strong>Build it into routine upkeep.</strong> New pages, documents and plugins can introduce problems, so accessibility checks belong in your regular <a href="https://81.digital/website-support-services/">website support and maintenance</a>.</li>
</ol>
<p>If your site is bilingual, remember that the Welsh and English versions are both part of your website, so both need to meet the same standard. There is more on this on the <a href="https://81.digital/bilingual-accessible-websites/">bilingual and accessible websites</a> page.</p>
<h2>Frequently asked questions</h2>
<h3>Our charity gets some council funding. Are we covered by the accessibility regulations?</h3>
<p>Only if you are mostly publicly funded, provide services essential to the public, or your services are aimed at disabled people. Some grant funding on its own does not bring you under the regulations, but the Equality Act duty to make reasonable adjustments still applies.</p>
<h3>Is WCAG 2.1 still enough?</h3>
<p>The current government guidance names WCAG 2.2 AA as the standard for public sector bodies. If your site already meets 2.1 AA, you are most of the way there and need to check the six new A and AA criteria.</p>
<h3>Do we have to fix all our old PDFs?</h3>
<p>Not usually. Documents published before 23 September 2018 are exempt unless people need them to use your services, such as an application form. Newer documents are covered, so it is often easier to publish key information as web pages instead.</p>
<p>If you would like a second opinion on your website&#8217;s accessibility or help writing an accessibility statement, <a href="https://81.digital/contact/">get in touch with 81 Digital</a>.</p>
<p>The post <a href="https://81.digital/blog/charity-website-accessibility-regulations/">Do Charity and Public Sector Websites Have to Meet Accessibility Regulations?</a> appeared first on <a href="https://81.digital">Eight One Digital</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>How to Move to Shopify and Protect Your Google Rankings</title>
		<link>https://81.digital/blog/move-to-shopify-without-losing-rankings/</link>
		
		<dc:creator><![CDATA[Hywel]]></dc:creator>
		<pubDate>Sat, 24 Oct 2026 21:50:10 +0000</pubDate>
				<category><![CDATA[Guides]]></category>
		<guid isPermaLink="false">https://81.digital/2026/10/24/move-to-shopify-without-losing-rankings/</guid>

					<description><![CDATA[<p>Moving to Shopify from WooCommerce, Wix or Square? Here is how to keep the Google rankings you have built up.</p>
<p>The post <a href="https://81.digital/blog/move-to-shopify-without-losing-rankings/">How to Move to Shopify and Protect Your Google Rankings</a> appeared first on <a href="https://81.digital">Eight One Digital</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Moving your online shop to Shopify from WooCommerce, Wix, Square or another platform can be a big step forward. If it isn&#8217;t handled properly, though, it&#8217;s also one of the easiest ways to lose the Google rankings you&#8217;ve built up. Here&#8217;s what needs to happen to avoid that.</p>
<h2>Why rankings drop after a move</h2>
<p>When you change platform, your page addresses almost always change. Shopify uses its own structure, with products under /products/, collections under /collections/ and pages under /pages/. If Google visits your old addresses and finds nothing, those pages drop out of the search results and any links pointing to them are wasted.</p>
<h2>1. List every URL on your current site</h2>
<p>Before anything else, get a full list of your current pages, products, categories and blog posts. Your sitemap, a crawling tool or Google Search Console can all help. Pay most attention to the pages that bring in traffic and sales.</p>
<h2>2. Map old addresses to new ones</h2>
<p>Match each old URL to the closest page on the new Shopify store. A product should point to the same product, and a category to the matching collection. Avoid sending everything to the homepage, as Google treats that much like a missing page.</p>
<h2>3. Set up 301 redirects</h2>
<p>A 301 redirect tells Google a page has moved permanently and passes on most of its value. Shopify has a built-in URL redirect tool, and redirects can be imported in bulk from a CSV file, which is the only sensible way to do it for a big catalogue.</p>
<h2>4. Keep your titles, descriptions and content</h2>
<p>Carry over page titles, meta descriptions, product descriptions and image alt text rather than starting from scratch. If a page ranks well now, keep what&#8217;s working.</p>
<h2>5. Check everything after launch</h2>
<p>Once the new store is live, submit the new sitemap in Google Search Console and keep an eye on the Pages report for errors over the following weeks. Test a sample of old URLs to make sure they redirect properly.</p>
<h2>Expect a short wobble</h2>
<p>Even a well-handled move can cause a small dip for a few weeks while Google catches up. With redirects in place, rankings usually settle back down. Without them, they often don&#8217;t.</p>
<h2>Need a hand?</h2>
<p>I move shops to Shopify with redirects, SEO checks and data migration handled properly. Have a look at my <a href="/shopify-website-design/">Shopify</a> and <a href="/shopify-seo/">Shopify SEO</a> pages, or <a href="/contact/">get in touch</a> to talk about your move.</p>
<p>The post <a href="https://81.digital/blog/move-to-shopify-without-losing-rankings/">How to Move to Shopify and Protect Your Google Rankings</a> appeared first on <a href="https://81.digital">Eight One Digital</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Shopify or WordPress: Which Is Right for Your Business?</title>
		<link>https://81.digital/blog/shopify-or-wordpress/</link>
		
		<dc:creator><![CDATA[Hywel]]></dc:creator>
		<pubDate>Sat, 24 Oct 2026 21:50:08 +0000</pubDate>
				<category><![CDATA[Guides]]></category>
		<guid isPermaLink="false">https://81.digital/2026/10/24/shopify-or-wordpress/</guid>

					<description><![CDATA[<p>Both are good platforms. Here is how to decide which one suits your business, from someone who builds on both.</p>
<p>The post <a href="https://81.digital/blog/shopify-or-wordpress/">Shopify or WordPress: Which Is Right for Your Business?</a> appeared first on <a href="https://81.digital">Eight One Digital</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>It&#8217;s one of the questions I get asked most. I build on both, so this isn&#8217;t a sales pitch for one over the other. The right answer depends on what your website actually needs to do.</p>
<h2>The short answer</h2>
<p>If selling products online is the main point of your website, Shopify is usually the better choice. If your website is mainly there to explain what you do and bring in enquiries, bookings or applications, WordPress is usually the better fit.</p>
<h2>When Shopify makes sense</h2>
<ul>
<li>You sell physical products and want a shop that just works, with payments, shipping, stock and orders handled in one place.</li>
<li>You want to run the shop day to day yourself without worrying about updates, security or hosting.</li>
<li>You have a physical shop too and want in-store and online sales in one system.</li>
<li>You expect to grow and don&#8217;t want to rebuild in a couple of years.</li>
</ul>
<p>The trade-off is less flexibility in some areas. Shopify has a fixed URL structure, some features need apps, and there&#8217;s an ongoing monthly subscription.</p>
<h2>When WordPress makes sense</h2>
<ul>
<li>Your website is about services, information or content rather than products.</li>
<li>You need things like job listings, bookings, memberships or Welsh and English versions of every page.</li>
<li>You want full control over the design, structure and content.</li>
<li>You want to own the site outright and be free to move hosts or developers whenever you like.</li>
</ul>
<p>The trade-off is that WordPress needs looking after. Core, theme and plugin updates, backups and security checks all need doing regularly, which is where a support plan comes in.</p>
<h2>What about WooCommerce?</h2>
<p>WooCommerce adds a shop to WordPress, and it works well for some businesses, especially when the shop is a small part of a bigger content site. Where selling online is the main thing, I find Shopify is usually easier to run and less work to maintain.</p>
<h2>Running costs to think about</h2>
<p>Shopify has a monthly plan, plus the cost of any paid apps you need. WordPress itself is free, but you&#8217;ll pay for hosting, any premium plugins or themes, and ongoing maintenance. Neither is automatically cheaper. It depends on what you need the site to do.</p>
<h2>Still not sure?</h2>
<p>Tell me what you sell or offer, and how you want people to buy from you or get in touch, and I&#8217;ll give you a straight answer on which platform suits you. <a href="/contact/">Get in touch</a>, or have a look at my <a href="/shopify-website-design/">Shopify</a> and <a href="/website-design/">WordPress website</a> pages.</p>
<p>The post <a href="https://81.digital/blog/shopify-or-wordpress/">Shopify or WordPress: Which Is Right for Your Business?</a> appeared first on <a href="https://81.digital">Eight One Digital</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
