<?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>Alessandro Tei</title>
	<atom:link href="https://www.alessandrotei.com/en/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.alessandrotei.com/en/</link>
	<description>Siti WordPress a Firenze, fatti bene e seguiti nel tempo</description>
	<lastBuildDate>Tue, 27 Oct 2026 17:27:24 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.5</generator>

<image>
	<url>https://www.alessandrotei.com/wp-content/uploads/2026/10/tei-icona-150x150.png</url>
	<title>Alessandro Tei</title>
	<link>https://www.alessandrotei.com/en/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Five signs it&#8217;s time to rebuild your website</title>
		<link>https://www.alessandrotei.com/en/when-to-rebuild-your-website/</link>
					<comments>https://www.alessandrotei.com/en/when-to-rebuild-your-website/#respond</comments>
		
		<dc:creator><![CDATA[Alessandro Tei]]></dc:creator>
		<pubDate>Tue, 27 Oct 2026 17:27:24 +0000</pubDate>
				<category><![CDATA[Senza categoria]]></category>
		<guid isPermaLink="false">https://www.alessandrotei.com/?p=906</guid>

					<description><![CDATA[<p>You don't need a new website every two years. But there are times when fixing it costs more than starting from scratch.</p>
<p>L'articolo <a href="https://www.alessandrotei.com/en/when-to-rebuild-your-website/">Five signs it&#8217;s time to rebuild your website</a> proviene da <a href="https://www.alessandrotei.com/en/">Alessandro Tei</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>A website doesn&#8217;t go off like yoghurt, but it does age. Sometimes fixing it is enough; sometimes patching it costs more than starting over. These are the signs that, after eleven years of working on WordPress sites, tell me it&#8217;s time for a new one, with a way to check each of them yourself.</p>
<h2>1. It can no longer be updated</h2>
<p>Old versions of WordPress or PHP, themes abandoned by their authors, plugins that break something with every update. It&#8217;s the most common case and the riskiest: a site that can&#8217;t be updated is easier to hack.</p>
<p><strong>How to check:</strong> in your WordPress dashboard go to Tools, then Site Health. If you see warnings about outdated PHP or themes and plugins that haven&#8217;t been updated in years, you have a problem. If the theme hasn&#8217;t had an update for a long time, it&#8217;s unlikely to get one in future.</p>
<h2>2. It&#8217;s awkward on a phone</h2>
<p>Most visits now come from smartphones. If people have to zoom in to read, the buttons are tiny or the menu won&#8217;t open properly, you&#8217;re losing enquiries without knowing it. Google also judges websites mainly on how they work on mobile.</p>
<p><strong>How to check:</strong> try doing the three things a customer needs to do on your phone, such as finding a service, reading your opening hours and contacting you. If it&#8217;s hard work for you, it&#8217;s hard work for them.</p>
<h2>3. It&#8217;s slow</h2>
<p>If the site takes many seconds to load, some people leave before they see it. The usual culprits are heavy themes, outdated page builders, huge images and dozens of plugins piled up over the years.</p>
<p><strong>How to check:</strong> enter your address in Google&#8217;s PageSpeed Insights and look at the mobile result. If the scores are low and the suggestions point to the theme or page builder, slimming it down may not be enough.</p>
<h2>4. You can&#8217;t edit it yourself</h2>
<p>If you have to call someone to change your opening hours, add an event or swap a photo, the site is working against you. A good website can be updated in minutes by the people who use it every day.</p>
<p><strong>How to check:</strong> think of the last change you wanted to make and didn&#8217;t. If the answer is &#8220;too many&#8221;, the problem isn&#8217;t you, it&#8217;s how the site was built.</p>
<h2>5. It no longer represents you</h2>
<p>New services, a new logo, a business that has grown, customers different from five years ago. Your website should tell people who you are today. If you send the link with a touch of embarrassment, or avoid sending it at all, that&#8217;s a clear sign.</p>
<p><strong>How to check:</strong> read your home page as if you were a new customer. Can you tell within seconds what you do, who for, and how to get in touch?</p>
<h2>One more sign: the rules have changed</h2>
<p>Privacy, cookie and accessibility rules have changed in recent years. Since 28 June 2025, for example, the European Accessibility Act has required certain digital services, such as online shops, to meet accessibility standards. Microenterprises providing services are exempt, but a website everyone can use is worth having anyway. If your site was built before these rules, it should at least be checked.</p>
<h2>Fix or rebuild: how to decide</h2>
<p><strong>Fix it</strong> when the foundations are sound: the theme is maintained, the structure works and the problems are specific, such as a plugin to replace, images to optimise or a few pages to rewrite.</p>
<p><strong>Rebuild it</strong> when the problems are structural: an abandoned theme, a heavy page builder, versions that can&#8217;t be updated, content that needs rethinking. In these cases every fix is a patch, and the patches end up costing more than a new site.</p>
<p>A new website doesn&#8217;t mean losing what you&#8217;ve built. Pages already found on Google can be kept or redirected, good content can be reused, and you start from a base that will last for years.</p>
<h2>Not sure?</h2>
<p>With a fixed-price check-up I look at your website and tell you in writing whether it&#8217;s worth fixing or rebuilding, and what each option would cost. If fixing it makes more sense, I&#8217;ll say so, even if it means less work for me. You&#8217;ll find the details under <a href="/en/services/wordpress-support-florence/">WordPress support</a>; if you&#8217;d rather start afresh, have a look at <a href="/en/services/business-websites-florence/">websites for professionals and small businesses</a> and some <a href="/en/work/">recent work</a>. Or <a href="/en/contact/">book a 20-minute call</a> and we&#8217;ll talk it through.</p>
<p>L'articolo <a href="https://www.alessandrotei.com/en/when-to-rebuild-your-website/">Five signs it&#8217;s time to rebuild your website</a> proviene da <a href="https://www.alessandrotei.com/en/">Alessandro Tei</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.alessandrotei.com/en/when-to-rebuild-your-website/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>How much does a website really cost in 2026</title>
		<link>https://www.alessandrotei.com/en/how-much-does-a-website-cost/</link>
					<comments>https://www.alessandrotei.com/en/how-much-does-a-website-cost/#respond</comments>
		
		<dc:creator><![CDATA[Alessandro Tei]]></dc:creator>
		<pubDate>Tue, 27 Oct 2026 17:27:12 +0000</pubDate>
				<category><![CDATA[Senza categoria]]></category>
		<guid isPermaLink="false">https://www.alessandrotei.com/?p=901</guid>

					<description><![CDATA[<p>From 300 to 10,000 euros: why quotes vary so much and what to ask so you can compare them without surprises.</p>
<p>L'articolo <a href="https://www.alessandrotei.com/en/how-much-does-a-website-cost/">How much does a website really cost in 2026</a> proviene da <a href="https://www.alessandrotei.com/en/">Alessandro Tei</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Ask three people to quote for a website and you get three figures that look nothing alike: 400 euros, 1,800, 6,000. It isn&#8217;t always bad faith. Usually you are being quoted for three different things, written in a way that hides it. In this guide I explain what really drives the price, which costs come after launch and what to ask so you can compare offers without surprises. The figures refer to small businesses in Italy, but the logic applies anywhere.</p>
<h2>Why quotes differ so much</h2>
<p>A website isn&#8217;t an off-the-shelf product. The same word covers a ready-made theme with your logo on it and a project built around your customers, with copy written for Google and someone who looks after it after launch. The price changes mainly for three reasons:</p>
<ul>
<li><strong>How much is built for you.</strong> Adapting a template is quick. Designing the structure, user journeys and pages around what you do takes longer, and it shows in the result.</li>
<li><strong>What is included.</strong> Privacy, cookies, search optimisation, training and support after launch are sometimes included, sometimes not, and sometimes turn up as extras.</li>
<li><strong>Who builds it.</strong> An agency has higher overheads than a freelancer. In return it can put several specialists on the same project.</li>
</ul>
<h2>What makes up the price</h2>
<ul>
<li><strong>Number and type of pages.</strong> Five fixed pages cost less than a filterable archive of projects, events or products.</li>
<li><strong>Languages.</strong> Each extra language means extra work, even if you provide the translations: menus, forms, SEO and checks have to be done for every version.</li>
<li><strong>Content.</strong> Ready copy and photos shorten the timeline. Writing them from scratch, or organising a photo shoot, is separate work and should appear in the quote.</li>
<li><strong>Features.</strong> Bookings, a small shop, members&#8217; areas, connections to management or booking systems. Each one has to be set up, tested and maintained.</li>
<li><strong>Design.</strong> Creating a logo and visual identity is a project in itself. If you already have them, work on the site can start sooner.</li>
</ul>
<h2>The costs that come after launch</h2>
<p>The cost of the website is only the start. Your budget should also cover the recurring costs that low quotes often leave out:</p>
<ul>
<li><strong>Domain</strong>: usually a few tens of euros a year for a .it or .com.</li>
<li><strong>Hosting</strong>: from a few tens to a few hundred euros a year, depending on speed, backups and the provider&#8217;s support. Hosting that is too cheap is paid for in slowness and problems.</li>
<li><strong>Licences</strong>: some professional plugins and themes renew every year. Always ask which ones and how much they cost.</li>
<li><strong>Maintenance</strong>: updates, backups and security checks. WordPress needs regular updates; a site left to itself becomes slow and vulnerable.</li>
</ul>
<p>The domain and hosting should always be in your name, not the developer&#8217;s. If you change provider one day, the website stays yours.</p>
<h2>Three price ranges to help you get your bearings</h2>
<p>Market prices vary a lot. Broadly, for a small business in Italy:</p>
<ul>
<li><strong>Under 500 euros</strong>: usually an adapted template, a few pages and little or no support afterwards. It may be enough to get started, but ask carefully what happens when something breaks.</li>
<li><strong>From around 800 to 3,000 euros</strong>: professional, made-to-measure websites for practices, shops, restaurants and associations, with a well-planned structure, basic SEO, privacy compliance and training.</li>
<li><strong>Above that</strong>: projects with many languages, complex archives, larger online shops, integrations with other systems or several specialists involved.</li>
</ul>
<p>What&#8217;s inside matters more than the figure. Two quotes can only be compared line by line.</p>
<h2>What to ask before you sign</h2>
<ul>
<li>How many pages and sections are included, and what does adding more cost?</li>
<li>Who writes the copy and who takes care of the photos?</li>
<li>Are privacy, cookies and search optimisation included?</li>
<li>Will I be able to edit text, images and pages myself? Is training included?</li>
<li>Will the domain and hosting be in my name?</li>
<li>What happens after launch: who updates the site, who handles backups, and what does it cost?</li>
<li>What is the timeline, and what do you need from me to keep to it?</li>
<li>For non-Italian speakers: will we work in English, and will all documents and training be in English too?</li>
</ul>
<p>If a quote doesn&#8217;t answer these questions, ask for the answers in writing. It&#8217;s the simplest way to avoid surprise extras.</p>
<h2>My prices, as a guide</h2>
<p>A <a href="/en/services/business-websites-florence/">website for professionals and small businesses</a> starts at 800 euros, a <a href="/en/services/custom-multilingual-websites-florence/">custom or multilingual website</a> at 1,500 euros. Both include the first year of maintenance. <a href="/en/services/wordpress-support-florence/">Support for existing websites</a> costs 40 euros an hour and starts with a fixed-price check-up. I work in English with international clients.</p>
<p>After a 20-minute call I send you a written proposal with three options, each with its items, timeline and costs. You decide how much to invest, knowing exactly what you get. <a href="/en/contact/">Book a call</a> whenever suits you.</p>
<p>L'articolo <a href="https://www.alessandrotei.com/en/how-much-does-a-website-cost/">How much does a website really cost in 2026</a> proviene da <a href="https://www.alessandrotei.com/en/">Alessandro Tei</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.alessandrotei.com/en/how-much-does-a-website-cost/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Hacked WordPress site: what to do in the first 24 hours</title>
		<link>https://www.alessandrotei.com/en/hacked-wordpress-site-what-to-do/</link>
					<comments>https://www.alessandrotei.com/en/hacked-wordpress-site-what-to-do/#respond</comments>
		
		<dc:creator><![CDATA[Alessandro Tei]]></dc:creator>
		<pubDate>Tue, 27 Oct 2026 17:26:58 +0000</pubDate>
				<category><![CDATA[Senza categoria]]></category>
		<guid isPermaLink="false">https://www.alessandrotei.com/?p=897</guid>

					<description><![CDATA[<p>Strange redirects, pages in Japanese, Google flagging your site as dangerous. What to do straight away, in order, to limit the damage.</p>
<p>L'articolo <a href="https://www.alessandrotei.com/en/hacked-wordpress-site-what-to-do/">Hacked WordPress site: what to do in the first 24 hours</a> proviene da <a href="https://www.alessandrotei.com/en/">Alessandro Tei</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>You almost always find out by chance. A customer tells you your site is opening strange pages, Google shows a red warning, search results in Japanese appear under your domain, or your hosting provider suspends your account. A hacked WordPress site is serious, but with the right steps it can almost always be recovered. This is the sequence I follow, in the order it makes sense to do it.</p>
<h2>How to tell if your site has been hacked</h2>
<ul>
<li>The site redirects visitors elsewhere, often only on mobile or only when they arrive from Google.</li>
<li>Pages you never created show up on Google, sometimes in other languages.</li>
<li>Your browser or Google flags the site as dangerous.</li>
<li>You find administrator accounts you don&#8217;t recognise.</li>
<li>The site has become very slow, or your host reports unusual resource use or outgoing spam.</li>
</ul>
<p>Even one of these signs is worth checking. The longer you wait, the further the problem spreads and the harder it is to clean up.</p>
<h2>1. Don&#8217;t delete anything, make a copy</h2>
<p>The first instinct is to delete suspicious files or reinstall everything. Before that, make a full copy of the files and database exactly as they are, and store it off the server. You need it to understand how the attackers got in and to avoid losing content you may not have anywhere else. If your host has backups from before the attack, note their dates: they may come in handy.</p>
<h2>2. Limit the damage</h2>
<p>If the site is sending visitors to malicious pages, put it into maintenance mode or ask your host to block it temporarily. A few hours offline is better than customers landing on scam sites under your name.</p>
<h2>3. Change every password</h2>
<p>WordPress logins for every administrator, the hosting control panel, FTP or SFTP, the database and any email accounts on the domain. If you use the same password elsewhere, change it there too. Also regenerate the WordPress security keys in wp-config.php: this logs out every open session, including the attacker&#8217;s.</p>
<h2>4. Check your administrator accounts</h2>
<p>Attackers often create an administrator with an anonymous-looking name, or change the email address of an existing user. Go through the list under Users, check emails and roles, and remove anyone you don&#8217;t recognise.</p>
<h2>5. Look for malicious code everywhere</h2>
<p>Modified files are only half the problem. There are many places to check:</p>
<ul>
<li>WordPress core files, compared against the originals;</li>
<li>themes and plugins, including inactive ones;</li>
<li>the uploads folder, which should not contain PHP files;</li>
<li>files such as .htaccess and wp-config.php, and the mu-plugins folder;</li>
<li>the database: modified options, scripts injected into posts, hidden users and scheduled tasks that reinstall the malware.</li>
</ul>
<p>Security scanners help find the bulk of it, but they are not enough on their own. This is where experience counts: a half-finished clean-up brings the problem back within days.</p>
<h2>6. Reinstall from clean sources and update everything</h2>
<p>WordPress, the theme and plugins should be reinstalled from official sources, not restored from the infected files. Then bring everything up to the latest version. Abandoned plugins, or ones downloaded from unofficial sites, need replacing: they are among the most common ways in.</p>
<h2>7. Ask Google to review the site</h2>
<p>If Google flagged the site, once it is clean open Search Console, check the Security issues report and request a review. When the review succeeds, the warning disappears. If spam pages were created, make sure they don&#8217;t stay indexed.</p>
<h2>8. Consider your data protection duties</h2>
<p>If customer data passes through the site, such as contact forms, orders or accounts, a breach may involve that data too. Under the GDPR, the data controller must notify the supervisory authority of breaches likely to put people at risk within 72 hours of becoming aware of them. If in doubt, talk to whoever handles privacy for your business straight away.</p>
<h2>How to stop it happening again</h2>
<ul>
<li>Regular updates for WordPress, the theme and plugins.</li>
<li>Automatic backups stored off the server, and tested now and then.</li>
<li>Strong, unique passwords, with two-factor authentication for administrators.</li>
<li>Few plugins, well chosen and maintained by their authors.</li>
<li>Someone who checks the site regularly and spots problems before you do.</li>
</ul>
<p>That is exactly what I do with <a href="/en/services/wordpress-maintenance-florence/">WordPress maintenance</a>.</p>
<h2>When to ask for help</h2>
<p>If your website matters to your business, don&#8217;t lose days to trial and error. With <a href="/en/services/wordpress-support-florence/">WordPress support</a> I start with a fixed-price check-up: I tell you what happened, what it takes to really clean the site and how to prevent it from happening again. I also work on sites built by others. <a href="/en/contact/">Write to me</a> or call me: in emergencies I reply the same day.</p>
<p>L'articolo <a href="https://www.alessandrotei.com/en/hacked-wordpress-site-what-to-do/">Hacked WordPress site: what to do in the first 24 hours</a> proviene da <a href="https://www.alessandrotei.com/en/">Alessandro Tei</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.alessandrotei.com/en/hacked-wordpress-site-what-to-do/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
