AD
Episode
531
Interview
Web News

How to Make a Website: 4 Decisions You Need to Make First

Recorded:
November 4, 2026
Released:
November 17, 2026
Episode Number:
531

Building a website is easier than ever, but choosing how to build it shouldn't be your first step. Matt and Mike break down four important decisions to make before choosing a platform, hiring a developer, or asking AI to build your website. From identifying essential features to planning maintenance, this episode provides a practical framework for starting your next website project.

Listen

Also available on...
...and many more, check your podcast app!

Who’s in This Episode?

Show Notes

Introduction - Building a Website Is Easier Than Ever, Right?

  • This episode is not a step-by-step guide on how to make a website
    • There are too many options out there to make websites to cover in a single episode (ie Webflow, WordPress, React, Svelte, etc.)
    • Figuring out what you need from a website and how it will be run is arguably more important
  • Your website is a tool:
    • It needs to fulfill what you need and when you need it
    • It must be kept up-to-date and functional in order to perform those needs
  • Technology isn’t where your website journey should begin

Step 1: Determine What Your Website Needs to Do

You need to establish why the website needs to exist by asking: Why does this website need to exist?

Common Website Purposes

  • Informational Websites
    • Sites that provide business information, display services, share contact information, answer FAQ, establish creditability (ie. display testimonials)
  • Lead generation websites
    • Display actionable CTAs and pipelines (ie. quote request forms, booking consultations offers, call-back requests)
  • E-commerce websites
    • E-commerce sites sell products, process payments, manage inventory, handle logistics (shipping rates, customs fees, taxes)
  • Content-focused websites
    • These sites are content-rich with blog posts, sharing mechanisms (RSS feeds for blog posts/news), and host podcasts. They’re designed to help build an audience, affiliate revenue, and display advertising.
  • Web applications
    • Web apps accomplish tasks via interactive tools, provide custom functionality (ie organizing a TCG collection), allow users to make accounts, and provide analytical dashboards where appropriate

Identify Your Required Features

Once you know the purpose, you can start identifying features.

  • Common website features
    • Contact forms
    • Photo galleries
    • Booking systems
    • Content Management Systems (CMS)
    • Search functionality
    • Newsletter subscriptions
    • Online stores
  • Be quick to identify needs versus wants
    • You need your website to serve your needs, you don’t need to have a million “cool features” that do nothing but collect dust
    • Remember your website is a tool

Step 2: Decide Who Will Maintain the Website

Now that we’ve determined that we need a website, and what needs to be on there - it’s time to decide who will maintain the website.

Time and time again, people will develop their entire website only to realize that nobody has the time to keep it up-to-date, which leaves it in disrepair. It is very crucial that you decide how your website will remain relevant to your business and ultimately to your customers. You do not want old information confusing potential customers, or broken pages turning people away.

Ask yourself: Who's responsible for keeping this website running and accurate?

Websites Aren't Necessarily Set-and-Forget

  • Once your website launches, things can change on the business:
    • Business hours (including holiday hours)
    • Prices
    • Services added/removed/seasonal
    • Contact information changes
  • Once your website launches, things can change on the technical side:
    • Software requires updates
    • Security vulnerabilities are discovered (especially in the age of AI)
    • Third-party connections evolve (ie your fav analytics plugin shuts down)
    • Domains and hosting need renewals
  • Once your website launches, things can change on the content side:
    • Written guides need their text updated
    • Images in photo galleries need updating after a reno
    • Publishing new posts and pages at the right time (ie holiday sale)
    • Creating new and maintaining old product pages
  • Once your website launches, things can change on the SEO side:
    • Google updates their parameters making your content plan out-of-date
    • Pages/content that once drove traffic are now detrimental to your rankings

Who Will Handle Maintenance?

Who will be responsible for your website updates? This shouldn’t be an abstract answer, it should be as concrete as you can make it in the moment.

  • You can have internal or external people maintain your site, common examples include:
    • The business owner
    • An employee
    • A freelancer
    • A web development agency
    • A managed website service
  • And you can split responsibility:
    • The owner is in charge of all pricing and business hours
    • Employee 1 is responsible for the blog content
    • Web dev agency is responsible for the security and software updates

How Often Will the Website Change?

It’s a good idea to have at least a rough plan on how frequent your website updates should be. The frequency of your site updates may dictate which tool(s) the site should be built with (ie do you need a CMS or blogging platform).

  • Low-frequency updates
    • Business information as needed
    • Occasional new photos, maybe seasonal
    • Yearly pricing changes
  • Medium-frequency updates
    • Monthly blog posts
    • Regular sales and promotions
    • New service pages (and their internal content)
  • High-frequency updates
    • Daily articles
    • Product inventory (especially in large product portfolios)
    • News websites and information-heavy blogs
    • Frequently changing content (ie events that are weather-dependent)

Step 3: Decide Who Will Build the Website

Now that you’ve determined what’s going to be on the website and who is going to be maintaining it after it’s made - it’s time to determine how it’s going to be developed.

This decision needs to consider your unique situation:

  • Budget
  • Available time
  • Technical knowledge
  • Design capabilities
  • Project complexity
  • Long-term maintenance requirements

Option A: Build It Yourself

  • Advantages
    • Potentially lower upfront costs
    • Complete control over the process
    • Opportunity to learn new skills
    • Easier to make changes independently
  • Disadvantages
    • Significant time investment
    • Learning curve
    • Potential design and usability issues
    • Risk of overlooking technical requirements
    • Troubleshooting can become difficult

Option B: Hire a Professional

  • Potential choices:
    • Freelance web developer
    • Web designer
    • Development agency
    • Full-service digital agency
  • Advantages
    • Professional expertise
    • Potentially faster delivery
    • Better handling of complex requirements
    • Guidance on platform selection
    • Access to design and development experience
  • Disadvantages
    • Higher upfront costs
    • Finding the right professional can be challenging
    • Potential ongoing costs
    • Dependence on someone else for certain changes

Option C: A Hybrid Approach

You don't necessarily have to do everything yourself or outsource everything.

Examples:

  • Hire a designer but build the website yourself.
  • Hire a developer to create the website, then manage the content internally.
  • Build the website yourself but hire someone for technical integrations.
  • Hire an agency for the initial project and use a freelancer for ongoing support.

Step 4: Choose How the Website Will Be Built

Now that we know what needs to be on our website, who will keep it up-to-date, and who will build it - it’s time to determine what technology we’ll use to build it.

We’re already three steps in so we have a tonne of data that will help direct our decision.

The question: Which approach or technology makes the most sense?

Important Note: You don't necessarily need to choose the technology yourself. If you're hiring a professional, they should help you make this decision and explain why their recommended approach fits your requirements.

Approach A: Website Builders

  • Examples: Wix, Squarespace
  • Best Suited For
    • Small businesses
    • Simple informational websites
    • Portfolios
    • Users with limited technical knowledge
    • People who want an integrated solution
  • Advantages
    • Relatively approachable
    • Hosting is generally included
    • Visual editing tools
    • Templates
    • Managed infrastructure
  • Considerations
    • Platform limitations
    • Recurring subscription costs
    • Potential difficulties migrating elsewhere
    • Less control over certain technical details

Approach B: Visual Development Platforms

  • Example: Webflow
  • Best Suited For
    • Design-focused websites
    • Marketing websites
    • Small and medium-sized businesses
    • Developers and designers who want visual control and instant internal feedback on design changes
  • Advantages
    • Significant design flexibility
    • Visual development environment
    • Built-in CMS capabilities
    • Managed hosting
    • Less need to write custom code for many common layouts
  • Considerations
    • Learning curve
    • Subscription costs
    • Platform-specific limitations
    • Some advanced functionality may require integrations or custom code

Approach C: Content Management Systems

  • Example: WordPress
  • Best Suited For
    • Blogs
    • Content-heavy websites
    • Business websites
    • Websites requiring extensibility
    • Projects with frequently updated content
  • Advantages
    • Large ecosystem
    • Extensive plugin availability
    • Flexible content management
    • Broad developer support
    • Self-hosting options
  • Considerations
    • Plugin compatibility
    • Security and maintenance responsibilities
    • Hosting decisions
    • Potential performance issues if poorly configured

Approach D: Custom Development

  • Examples: HTML/CSS/JavaScript, React, Next.js, SvelteKit
  • Best Suited For
    • Specialized functionality
    • Web applications
    • Complex integrations
    • Projects requiring significant customization
    • Teams with development expertise
  • Advantages
    • Greater architectural flexibility
    • Control over implementation
    • Ability to build highly specialized features
    • Freedom to choose infrastructure and integrations
  • Considerations
    • Development time
    • Higher technical requirements
    • Ongoing maintenance
    • Potentially higher costs
    • Greater responsibility for architecture and security

Approach E: AI-Assisted Website Development

  • Examples: AI website generators, prompt-based development tools, AI coding assistants.
  • Best Suited For
    • Rapid prototyping
    • Experimentation
    • Simple projects
    • Developers looking to accelerate workflows
    • Users comfortable evaluating AI-generated results
  • Advantages
    • Rapid initial development
    • Lower barrier to experimentation
    • Ability to generate layouts and functionality quickly
    • Can assist with coding and troubleshooting
  • Considerations
    • Understanding generated code
    • Security
    • Long-term maintainability
    • Debugging
    • Hosting and deployment
    • Platform dependence
    • Knowing what to do when something breaks

Important Notes

Note #1: AI can generate a website, but that doesn't necessarily mean the website is ready for production.

  • Questions worth asking when having AI make your website:
    • Who maintains the generated code?
    • What happens when the AI can't fix a problem?
    • Can someone else take over development?
    • Are you comfortable managing the hosting?
    • Does the website meet accessibility and security requirements?

Note #2: There is no universal best stack

The best technology depends on the project, but more often than not there will be concessions and workarounds that will be needed. For example, you might find the perfect technology, but it doesn’t fit your budget.

So it’s important to take this decision seriously, but not stay stuck on it forever. Perfectionism is the enemy here. Make a well-informed decision and then move forward. If your business’ needs change then you can always make a new website (or update your solution) down the road.



Links



How to support the show

Patreon

Prices subject to change and are listed in USD

  • Support the show from as little as ~$1/month
  • Get a shoutout at the end of the episode (while supplies last) for just ~$3/month
  • Help support the HTML All The Things Podcast: Click Here

Scrimba Discount - Coding Courses!

Learn to code using Scrimba with their interactive follow-along code editor.

Join their exclusive discord communities and network to find your first job!

Use our affiliate link for a 20% discount!!

  • Click the link to take you to the Scrimba site
  • A pop-up should appear on your screen with the discount amount and instructions on how to claim it
  • Discount is for new accounts only

We receive a monetary kickback if you use our affiliate link and make a purchase.



Transcript

This transcript is machine generated, there may be errors.

[00:00:00]

Matt: So you've decided that you need a website, but now what? Do you jump right into WordPress? Do you hire a developer? Do you do some Googling, find Wix or Webflow and start diving into that? Maybe you just ask AI to build the whole thing out for you. There are many ways these days to make a website, possibly more than ever before, especially with AI tacked onto there.

But that doesn't necessarily make the process any easier. The problem is that many people start by figuring out how they're going to build their website before they've figured out what they actually need. So in this episode, we're breaking down the four major decisions you should make when creating a website.

So we're not gonna teach you, how to code React and things like this. What we're gonna be talking about is the actual four-step procedure that I use on a lot of my small business clients when I have a conversation with them. This is the process that I initiate. If you're a DIYer, this also applies to you as well, because you can apply this kind of four-step procedure or [00:01:00] this four-step framework in order to get a website off the ground and hopefully be successful.

So if this sounds interesting to you and you wanna support the show, you can go and check us out on that Patreon, leave a review or rating in your podcast app, join us in our Discord server, or share this with your friends. And if you wanna learn how to code, Scrimba's got some courses for you, and you can get up to 20% off a Scrimba Pro plan if you use our link.

Our link will be in the RSS description as well as in the show notes with details on how that link works in the show notes on htmlallthethings.com. And so Mike, once again, another week, another main takeaway before we jump into this loaded episode. What was your main takeaway this week?

Mikhail: Good question. I, I I did not prepare one, uh, beforehand, but I w- I've been doing a lot of, like, security mitigations, most of my work these days is just making sure that all of our apps and services that we have built are [00:02:00] not susceptible to the latest vulnerabilities, which are happening every day. and I'm just starting to realize that the standard developer might be, might have to transition to be, like, a security engineer, and that might put people in a better position to sell themselves. Because right now, like, you can see everywhere just everything's getting pwned. And if you present yourself as a developer, great, but if you present yourself as a developer that can develop responsibly and has a good depth knowledge of security so you have kind of both assets, I feel like that's the way to go.

I'm, I'm exploring it a little bit. I'm talking to people in the industry right now about it a lot, so I might have an episode on this, honestly, in the future. so stay tuned for that. But that's kind of been top of mind for me is trying to figure out what a security-minded engineer... Obviously, they've been around for a while, but what does it look like in the, in today's day and age?[00:03:00]

Matt: I have a, a sustainability concern with that though, and we can possibly get into it when you do your episode. But the sustainability concern that I have is that we're talking about devs taking on the development work. Oftentimes they're taking on the marketing work in terms of SEO. They're taking on a bunch of the other kind of side SEO/marketing work, which is understanding best practices with Google for Business, formerly Google My Business.

We're talking about, oh, remember to make sure everything's responsive and, and performance, so there's all the performance. Rem- remember now to make things secure, and we- we're always sort of adjacent to a lot of these things, including security of course, where it would be something as simple really as make sure your PHP is updated and make sure your WordPress plugins are up to date, just as a basic example.

But now it's like, hey, do all the, the server stuff, learn how to do all the server security and this and that, but also still do all of this stuff. Ultimately what we're boiling it down to is there's gonna be less of us regardless, [00:04:00] because if you're able to do everything and you're gonna have either an AI helping you or you're just expected to do everything, then why would you have a team, or especially a large team of people doing it for you?

Mikhail: Well, I think 100% there's gonna be less of us. Like, there- I don't think there's anyone that's debating that. what I'm trying to figure out is what does that look like? Is it, like, what is the team composition gonna look like in the future, right? Is it one guy doing literally everything? that's what managers want.

I don't know. That seems kind of like what you're saying. It, that seems like a pitfall. Like, it seems not feasible, but is it, like, instead of a team of five down to a team of two where one guy is, very much AI pilled and just goes, builds, builds, builds as fast as possible, and another guy, the other one is kind of like the yin, the yin-yangs approach where he's more of the security-minded person, and he reviews the stuff using AI, obviously, and makes sure that the infrastructure is secure and, and then, contributes to the fixes of the guy that's going, like, full speed.

I don't know. Like, it [00:05:00] Again, I'm, I'm kind of at the point where I'm just experimenting with this and just kind of trying to wrap my head around what, what that's gonna look like. But I think inevitably, yes, like, there's no doubt in my mind that there's gonna be much less of us that are needed for per project. it's just gonna change, and I'm wondering what it's gonna change to

Matt: Yeah, of course. I mean, you and I are not gonna be the ones that foretell the future. There's gonna be lots of estimates, lots of guesses, but from us and other people, and then eventually either someone will be right or mostly right or, or wrong completely and s- something comes out of left field, and all of a sudden all of us are wrong about everything.

Who knows? Who knows what the future holds? But it's, it's a sustainability concern is all, is all I'll say. I'll, we'll, we'll leave it if we, if you do a full episode on it, we'll leave that kind of conversation to that. but my main takeaway has been this week I've been trying to get more and more of our, o- outreach, going.

So Mike and I run a small business. We run a web dev agency, and [00:06:00] it's been referral and still is for a number of years. I mentioned this before. So I'm still working on outreach and, what I'm very, very quickly learning is that even if you are quick at doing the outreach stuff, you are still relying on other people, and so it is slow.

Make the posters, get everything ready, go talk to the person, the admin of a Facebook group, or go and talk to, a prospective client, or go and talk to... What you're doing is you're talking to people and because they have their own schedules, of course, you're not just entitled to their immediate time.

And so I might be ready, but they might not be. And so I'm kind of just all... But I have a bunch of pokers in the fire, and I'm just waiting, waiting, waiting and it's, it's... I mean, it's frustrating to say the least, but it's, it's good to know. I feel as though digital availability, especially with friends and maybe immediate colleagues, makes one think that things are gonna move faster when in reality, no.

That, [00:07:00] that's not the case. This person's on vacation. That person's unavailable. This person's on sabbatical. That person's working on a huge project. This person's trying to leave the industry. That person's trying to retire, et cetera, et cetera. So there's the, the people element to all this that we fail to identify, even though it obviously applies to us as well, because sometimes I'm the person element too.

Sometimes I'm working on this, and so I can't work on that naturally. So that's, that's my main takeaway for the week. It's just, it's slow-going. It's a slog, but the slog continues, I suppose But let's get into... The idea of this episode was how to build a website. That was the very first sort of thing I thought of.

And again, this is not a step-by-step tutorial. This is not going to teach you React. This is not gonna teach you JavaScript. This is not gonna teach you prompting. What this is gonna do is it's gonna talk about a four-step procedure or a four-step workflow for making a website.

We have to remember something before we get [00:08:00] started, is that a website largely is a tool. That tool can be entertainment and fun, and so that it's kind of less a tool and more just for fun. But if you're running a business, small business or otherwise, you need a website or at least so you think, which we'll get into.

You need a website, and how are you going to... What are you gonna do on that website? You have to think this through. Your website is a tool, and it needs to fulfill the needs of your business. It needs to fulfill the needs of your business efficiently. It needs to efficiently and sufficiently. It needs to fulfill those needs in order to basically lubricate your business more or less, for a lack of a better way to say it, but it also propels you.

Maybe you are trying to get leads from that business or from that website. Maybe you are trying to inform people of something. Maybe you are trying to provide something, such as documents from a document center or something like that. Maybe it's even a web app, and you're trying to provide some sort of service or tooling from that website, and [00:09:00] you need to look at the entire website as a tool.

It is not just something where, and this is what a lot of small businesses do when they approach us, they will come to me and say, "I, I need a website," but they don't know the, the purpose behind the website. They just think, "I'm making a new business," or, "I'm refreshing my current business. I need a website."

Why? What is the purpose of your website in relation to your business? What are you getting out of your website? And so that leads right into step one, again, of this four-step workflow, and that is to determine what your website needs to do. Now, here's the thing. You need to establish why the website needs to exist, and you need to ask yourself this question: Why does this website need to exist?

Point blank. Why does it need to exist? Many people will question in today's world, 'Hey, I have an Instagram account and I'm posting on Instagram, and I'm getting a, whole bunch of leads, and in fact, I'm getting so many leads I'm turning them [00:10:00] away. Do I need a website?' You might get stopped right now. Step one, you might get stopped and you might say, 'No, I don't need to have a website.

I don't need to, to have any more because I'm already overwhelmed.' But if you have any other concerns, and these are needs, right, of your business, such as I want to not only rely on Instagram, I don't wanna only rely on TikTok, I wanna have a spot on the internet that's mine where I control the information, I control the content, and I control the flow, then that's one of the reasons.

So what are some common website purposes? These are some things you can kinda rack your own brain and run through yourself and determine if these are any, any of these things are something you need. And it can be a combination of these things as well. Common website would be an information website.

That's something that'll provide business information like your hours of operation, what it is you do, what services you have, your contact information, how you'd like to be contacted Answers frequently asked questions, things that you don't wanna field phone [00:11:00] calls for, things where you want people to just be able to quick- quickly check, and they can get that answer 24/7, 365.

You also wanna establish your credibility. Have you been doing landscaping for a long time? do you have happy customers? What have you done? Have you done a whole bunch of lawn cutting and not so much of the outside sort of tiling work and working on patios? Or are you mostly doing patio and stone work,

is that your, your bread and butter? Are you 50/50? Are you doing both of them and you're getting great reviews for both of them? That's an information website. This is a place for you to display your information. Now, I know what someone out there is gonna say, "Well, I display that information on my Instagram.

I display that information on my social media." That's great, but here's the thing. Social media is out of order, especially when it comes to algorithmic delivery. So you might, you might come in and say, "Here's my hours of operation," and you post that today. Someone in a month might see that, but they never got to see your portfolio post, [00:12:00] and they'd have to go to your actual post to look at it at all.

So now you can, you can pin some posts, and you can kind of direct people a certain way. You can have story highlights, for example, on Instagram and things like that. Absolutely, you can do that, but the thing is, everything is still out of order. Everything is not as super concise. When you go to the website, you go to the homepage.

It's an introduction. You go to the About page. Someone knows what they're looking at. You go to the Services page. Someone knows what they're getting. It's very direct. It's basically question, answer, question, answer. And that leads to the next type of common website, which would be for lead generation. Th- this type of website will display actionable CTAs.

Lead generation websites. So these are websites that actually display CTAs or calls to action, and they oftentimes have pipelines. So for example, you might have something like you've taken out a Facebook ad, someone clicks on your Facebook ad, it leads you to a landing page, and that landing page has a quote request form, [00:13:00] or it has a booking page, or it has a, a consultation request, right?

Maybe you're running a promotion where you're going to the first 50 customers get a free assessment of their driveway because you're gonna be doing the stonework on their driveway, first 50 customers. So that's a, that's a lead generation website, right? You SEO that page. Maybe you do take out ads. You lead someone to that form, to that call to action, and there you go.

Callbacks as well, maybe you want people to call you. Maybe you want people to leave their number for them to call or for you to call them back. These are lead generation websites. It's people that have shown up via one means or another, whether that be the Facebook ad, whether that be direct, whether that be through Google, et cetera, et cetera, and they're gonna research your, your page.

They're gonna look at your offering, and then they're going to do an action, and now they're sort of a warm lead, or I'd call them more of a lukewarm lead, but they're a, warm lead. They're more than just a random stranger in your Google Analytics

Mikhail: I'd argue, the [00:14:00] first two, like you said, be combined. I'd almost say that every informational website is a lead generation website, and I get that there might be some that are strictly, like who cares about the lead or who cares about getting the, you know, the person in. even then, the fact that if someone lands on that website and then finds the contact information and calls you, that in itself is lead generation.

Do you know what I mean? Maybe it's like very static lead generation, not intentional lead generation, but it is lead generation. But like it's the hierarchy, right? Like the informational, and then it leads to lead generation. And the other interesting thing about these two is like, I could say one confidently, like informational websites, if you're at all techy at all, like techy at all or even a little bit techy, if you have any idea of that, you can go to Squarespace and put together an informational website.

'Cause you don't care too much about the SEO. You know, you don't care too much about how the lead pipeline works. [00:15:00] You don't have a CRM to integrate, et cetera, et cetera, et cetera. There's just a lot of things that you don't need to worry about in a strictly informational website. then the next spot and the next type of common websites actually that, Matt is going to be talking about, Each one kinda leads to a more advanced agency that you're gonna have to hire or a more advanced developer that you're gonna have to hire, in my opinion, if you want a successful, something like fairly successful, right?

Because as soon as you go from just informational to lead generation, then you're talking a whole different tech stack. You're talking about potentially a CRM. You're talking about maybe making multiple landing pages all, all the time, like depending on campaign. Like you're talking about analytics.

You're talking about very advanced SEO. Like the step from information- from strictly informational to fully focused on lead generation is a pretty big one. So my advice to people, if you're listening to this and you're like, "You know, wh-which one do I fit in? Should I purchase, a package from an agency?

Should I just make it myself?" If you're just looking to get your information out there, [00:16:00] go to Squarespace or Wix, whatever. You know, like just get something out there, put something together. It might take you a couple hours. AI will help you there too. They all have AI. Great. If you look, want anything more, if you actually want money through the door, I would recommend, you know, giving an agency a call, giving a local developer a call, you know, look, doing your research, you know. If you need help with that, definitely, you know, you can give us a call as well. We can help you either find one or, or take care of it for you. But that's where I have the split. That's why I wanted to kinda bring it up here is that it's, it's right in this, in this area, this right in this region.

Matt: A lot of websites are certainly going to be lead generation, like you're saying. And lead generation, I will say, does have a degree of difficulty. And what I mean by that is you could just have a simple form, and you could do that on Square, or you could do that on Elementor, you could do that. But if you really want your CTAs to shine and you have a complex pipeline like Mike is talking about with CRMs, and you're trying to capture how [00:17:00] many people are showing up to the site and actually filling in the form, and how many of those requests actually turn into paying customers, things like that, it, like, the pipeline can absolutely get really complicated, and that also applies to e-commerce websites, which is another common website.

Obviously, the, an e-commerce website is meant to sell direct. So these websites will sell products. They will, of course, then process payments. They'll manage your inventory oftentimes. They'll handle logistics. they'll handle, the logistics which would be your shipping rates, your customs, fees, your taxes, things like that, and a lot of it's estimated and whatever, and it's obviously different per region and who you're shipping to and what you're shipping.

It's a kind of a whole mess. And so you can see kinda like what Mike was saying, where these, these start to get more and more complicated We do take a step, small step back though, when it comes to content-focused websites. So the thing here is, is these are sites that are content [00:18:00] rich with blogs, and this is sort of something like if you wanted to start a, a tech news website.

But in the modern era, a lot of the time you do need complex mechanisms installed on these type of websites. So these are websites that are content rich with blog posts. There's a lot of sharing mechanisms, so you'll have an RSS feed that shows up, that shows your blog posts or maybe shows a specific, set of blog posts, something in a specific category like tech or Apple or Android or whatever, things like that.

It might even host your podcast, and so these can get quite technically demanding, and you might need, customer software there, CRM software there as well. if you're openly selling ads, "Hey, buy this banner space. Hey, buy this. Hey, buy that," there's, uh, ways to track affiliate revenue, for example. just you have to display your advertising in a certain way, cookie pop-ups, you know, yada, yada, yada.

A lot of these apply to a lot of these different websites, but the thing is, is that [00:19:00] these progressively get more difficult. and then web apps, of course. Web apps accomplish, uh, tasks via interactive tools, of course. They provide custom functionality, like maybe you're trying to organize a TCG collection or something, and you use this web app to quickly do that, to organize your binders and whatnot.

they allow users generally to make accounts. They provide potentially analytical dashboards where appropriate to customers, and so there's a whole bunch of numbers being pulled in, and so now there's a security aspect. People are logging in. They're looking at numbers which could be confidential, or even if they're not logging in, they're using your website, they're using your webpage as a way to do something, get something out of it, such as, again, organizing a binder, organizing a TCG collection, which is a trading card game collection, things like that.

The thing here is those are just common website purposes. What we're ultimately trying to do is you're trying to identify, you're trying to identify the purpose, and then once you have the purpose, you go, "I want an informational website, I want lead generation, I want e-commerce." Once you [00:20:00] figure that out, now you need to identify the features.

This is still step one. We're still getting the framework ready here. We're still getting the framework of what it is you need and want and what type of website it is that you're actually going to try to create. Identify your required features. So things like, okay, because I want people to contact me, I need a contact form.

I do a ton of jobs and I take a ton of pictures, I want a photo gallery. I have very limited time and I want my calendar to be basically automated, I need a booking system. I want me and my staff to have access to all the blog posts, and we need to change things, and we need to write more blog posts, we need to write more news stories, I need a content management system.

My customers are going to use my website as a database of sorts, I need a search, a piece of search functionality of some kind. I want to reach out to my customers on a monthly basis, I need a newsletter subscription area, and then obviously an, a mail handler of some kind. [00:21:00] I want to sell to my customers, I need an online store the thing here, though, is be quick to identify need versus want.

I wanna go back to that principle of this website is a tool for you. It would be great if you needed a hammer and you were not sure what hammer to buy, so you bought ten hammers, and then you just used one. Fantastic. Here's the thing. You're gonna be using one, nine of them are gonna collect dust, and that was a waste of time and a waste of money.

You need to spend the time now to identify, in the hammer case, which hammer you want. Do the research, look at the reviews, yada, yada. Same with your website. You need to decide now, okay, I take a lot of photos, but I don't really like to upload them. Cut the photo gallery. I don't check my calendar. Cut the booking system.

I am not gonna get my staff to upload a lot. What CMS do I [00:22:00] really need? Or do I need a CMS, or can I simplify the CMS? Remember, your website's a tool. You don't want a bunch of wants collecting dust. You want your needs to actually be there and constantly updated and constantly working for you. You do not want a bunch of nonsense on your site.

We see this a lot with customer websites, a lot, when they'll say, "Well, one of these days I'll get around to X thing, so build me the feature." So they spend the money, they build the feature, which is great for me, of course. I'm the developer. I build them their website. I build them their document center. I build them their wiki, and then the wiki just sits there behind a password for years with just the sample articles that I built for them because they don't have the time, they didn't organize the time, none of that.

And that leads us to step two. You need to decide now, and I think this might be the most crucial step actually. You need to decide now who will maintain the website. This is extremely, extremely critical. [00:23:00] Time and time again, people will develop their entire website only to realize that nobody has the time to keep it up to date.

And what does this do? It leaves it in disrepair. It leaves pieces of information that are wrong. It leaves conflicting pieces of information. A classic one is you update your hours, not on your website, but only on your Google for Business profile, but they're still public on your, on your actual website.

So now people are getting two different versions of hours, and they're not sure when you're actually open. That not only confuses you, it's confusing to any of your customers, and it's confusing to your, to any bots, to AI bots. So if you want any reliable AEO, GEO, this stuff better be clear, concise, and updated.

You do not want your customers to get da-dated information. You do not want them to get incorrect information, which is usually because it's dated now. You do not want that. Now, here's the thing We live in the real world. Your website's not gonna be perfect. You're gonna make mistakes. You're gonna forget to do [00:24:00] things.

I do this, too. This is why we're making the decision now, though, because we're trying to be as prepared as possible. Websites are not necessarily set and forget. You need to choose what needs to be maintained and who is going to maintain those parts now.

It is probably the most crucial thing in this entire episode especially if it's a small business. Because you wear so many hats and you're running around a bunch, you've already distilled down your features and chosen which parts you don't want collecting dust, so I'm gonna cut it down to these three features, let's say.

those three features better be up to date and actually working for you and constantly maintained as needed

Mikhail: Yeah, it's tough to, like, picture this as a business owner. You're like, "Well, I b- I set my business hours once, and, like, I set my holiday hours. do I need this constantly maintained? Why do I need to purchase, like, a maintenance package, or why do I need to, you know, have an owner, maintaining the website?"

Like, you know, a marketing person inside your company or something like that. And the [00:25:00] reality is exactly what Matt was saying, that frustration from a customer that goes to the website and goes to Google or goes to your store and goes to the web- before that, goes to the website, and there's some sort of discrepancy, you have a potential chance to lose a customer.

Matt: 100%.

Mikhail: out.

Matt: Someone's gonna show up to your door and it's gonna be closed, and I've done that with, with businesses. I've shown up, closed, messaged them on Facebook. They're like, "Oh, we're closed on Thursdays." Well, I'm not coming back, so

Mikhail: Yeah, so you're, you'll lose the customer for life in the, in those situations, and you won't even notice it

Matt: yeah

Mikhail: 'cause they won't message you. you're, you're leaving significant money on the table if you do that. So I highly recommend you to listen to this advice, right? This doesn't have to be something that's overstrenuous.

It could be something that, hey, you work out once a quarter. if you really don't want people, you know, you don't, you don't wanna pay monthly or you don't wanna have a crazy amount of, having to constantly update something, okay, maybe once a quarter you go in, you give your web guy a call, and you're like, [00:26:00] "Hey, this is what's changing. This is what we should update. Hey, let's add this." This is the bare minimum, guys. this is the bare, bare minimum that you're keeping stuff up to date so that your customers have that knowledge. What you really need to be doing is, updating things, staying, staying on top of the latest trends on, how SEO works, how GEO works.

Right now is the most, is the fastest changing time we've probably ever had in our industry, and I guarantee you that your competitors are also feeling that as well. What I predict, in all industries, but in some industries, there's gonna be a war zone of people competing for their placements in the ChatGPT suggestions, in the SEOs on Google, with other people on a, on a more competitive basis because the agencies that are gonna be competing against them are all gonna be using AI. They're gonna be a continuously updating websites that are updated every month very heavily to try to optimize, and if you don't do that, and even if you're comfortable, you're resting on your laurels 'cause you have enough referral [00:27:00] traffic, it's a prime time that someone comes in and ta- eats your lunch. That is what's ha- gonna happen in my opinion in the next six months to, you know, 12 months to 16 months,

Matt: Well, it, it was always happening in, if you were in an SEO competitive field. If you just, just so happen to luck out with a random piece of content and it, it's number one, someone else, another SEO, is looking at that and is going to try to take your spot. There's a reason why SEOs are always fighting for top spot.

Remember, there's one top spot So they're gonna push somebody else out. Th- these aren't blank SERPs, search engine result pages. These aren't blank SERPs that are just being filled up. "Oh, I'll, I'll take the number one spot. I'm not pushing anyone out of the way." No, you're pushing people out of the way.

That's what SEOs do. That's what SEO does. It pushes people out of the way. And you me- you mentioned something really good there, Mike, is the, the frequency of updates, and in fact, in the show notes, I, I wrote down here that there are three sort of [00:28:00] frequency updates. Low-frequency updates, medium-frequency updates, and high-frequency updates, and you need to decide what fits in where.

Do you even have any high-frequency updates? Some people might just have like a landing page, maybe like two, three pages. You might not have any high-frequency updates. You might not even have any medium-frequency updates, but if you want your website to feel fresh and updated, maybe you have daily articles.

M- you wanna draw that back a bit? Okay, that's not a high-frequency update. Let's do a monthly blog post. There's a medium-frequency update, for example. Oh, I have a monthly sale. Better list that on your site somewhere, man. Don't just put it on Facebook with a, with an actual little advertisement or poster.

Put that on your website somewhere, and even if it's seasonal, I see people complain, I've heard people complain, "I don't wanna put this up every year." Draft that page, or make it so it's obvious that it's this year. If you h- hang Christmas lights once a year, and it's, it's from November to December, and you don't do it anymore, l- quite literally have a page there for hanging Christmas lights.

Do the SEO, yada, yada, yada. Make it clear that the information on the page is for [00:29:00] 2026. You can keep that page live if you want, and then you can update it next year for 2026. Or you can change stuff to TBD and things like that. Absolutely, 100%. But like Mike's saying, it, this is lowest hanging fruit.

You, you have to have these pages, and you have to have these pages, be actually up to date. There are various ways that information on a website would have to change. Things can change in the business side of things. So to categorize these, things can change on the business side of things. Business hours, this includes holiday hours, and also your holiday hours.

If you're a small business, it might just be you. You go on vacation for two weeks, you better say you're closed. Pricing. Prices go up and down all the time. They go all over the dang place, so there you go. Services. Add, remove, and seasonal. Just mentioned that. Contact information changes. Did your phone number change?

Do you have a more, preferred email? Maybe you found out that WhatsApp is a great way for you to drum up business. Change your contact information to [00:30:00] your WhatsApp. That's on the business side of things. But what about the technical side? We're not even really talking about technical this much this episode, but it's always gonna creep in.

Software requires updates. Mike, in your main takeaway, you were talking about security. you're gonna need to update your software. You're gonna need to take a look at those, those security vulnerabilities, especially in the, in the area of AI. Many people were caught off-guard with WordPress websites that were not on the appropriate PHP version Because WordPress is relatively customer facing, there are some customers that will just update their own plugins, but they need help updating PHP.

They don't know how to go into cPanel or Plesk or go into a Linux interface and change the PHP and then test the website and all that. They don't know how to do that. You also need to have people that make sure that your domains and your hosting get renewed. How many emergency phone calls have I had?

"The site's down, the site's down." I go, "Look, the server's up. I don't see anything wrong." Go to their website. Oh, they just didn't renew their domain, and that's their [00:31:00] email oftentimes too. Their email's in, in jeopardy now. Their, their website's in jeopardy. Their SEO is in jeopardy 'cause the website's down.

Hopefully no one took that domain. Hopefully, hopefully your registrar kept it for a couple of days or whatever. So you gotta have someone there and making sure the credit cards are up to date on those renewal accounts. Some people are buying domains for five years, and then of course they forget, and the credit card expires, and boom, there it goes.

So you have to have someone doing those technical things. And on the content side of things, what could potentially need to be updated? Written guides. Of course you're writing them, but what about updating them? What if you wrote a guide on how to do X thing and then now that methodology is completely different?

It might even be a legal thing where you're telling people, "Hey, you should do this." Oh, the law changes, you gotta do it this other way. Hopefully, you're gonna update that text. Images and photo galleries might need to be up to date. Do you really wanna have 10, 15-year-old pictures inside of your photo gallery?

Aren't you better at your craft now? Don't [00:32:00] you wanna show your latest work? What if you got the, the biggest project you've ever done just, just this month? You wanna show people that you're able to handle a project of that scale, don't you? So you wanna update your photo galleries. Publishing new posts and pages at the right time as well.

If you have specific landing pages where you're not really making an SEO play, but they're specific, maybe you took out a Facebook ad for a holiday promotion, you wanna make sure that an, that that new landing page or that new post goes out at the right time because you wanna make sure that your Facebook ad and that new page line up.

And what about creating and maintaining old product pages? This is a huge one that people miss all the time, and I always remind people to do this. You need to go into your old product pages and update them. If your product has changed in any way, "Oh, we have a slightly different purple color now," or this and that, you gotta change the pictures, man.

You gotta change the prices. You gotta change the SKU to line up with your inventory system if you have one, et cetera, et cetera. These are content changes that are very, very important. 'Cause if someone [00:33:00] orders it and it's a different shade of purple, they might send it back. So not only do you have an unhappy customer, now you're dealing with re- with refunds and things.

That's wasting your time, and that's wasting your money And once your website launches, things can and likely will change on the SEO front. And that's been the case for many, many years, where Google will just change what they prefer. You might have gone all in on a certain type of content, and now that certain type of content isn't top-notch.

Well, you might say, "Well, Matt, it's just not top-notch. I'm s-still making an SEO play." Great. What if Google's now punishing you for it now, though? Or that type of content is actually being punished? Well, now we need to go in and change things. We need to change our strategy. What if, what if pages that used to be crucial to driving traffic are now actually detrimental?

They're not just sitting there making nothing. They're actually hurting you now. You need to go in there and, and figure this out, and you need to figure out who will do this maintenance. It doesn't have to be just one person. You could [00:34:00] say the business owner is gonna do all the hours and all the, blog posts.

And then you could say all the staffers, because they're on the show floor, they're gonna do all of the products. They're gonna update the product pages. They're gonna take pictures of the products. They're gonna list the inventory. They're gonna be doing the inventory, et cetera. And it doesn't even have to be people within your business.

You could hire a web dev agency to help you. You can use a managed service, including, like, a-- getting an AI to help you, an AI agent. You could use a freelancer as well. Hire a freelancer, "Hey, I'm just gonna constantly send you images and constantly send you emails. You're gonna take that, you're gonna organize it, you're gonna put it into our CMS, and then the website's gonna update itself effectively."

So that way, you can rapid fire, go into your store, boom, boom, boom, boom, boom, picture, picture, picture, picture, write a little description, send an email. Now you don't worry about it. Site updates in a couple of days. Boom, there you go. Right? And remember, you can split this responsibility up. So it, it's not all crazy.

You're not necessarily having to hire somebody. You could just do it. You could split it up among two people that have just a little bit of time each. So now that you've decided all [00:35:00] this, you decided what's gonna be on the website and what you need on the website. You've also decided who's gonna be maintaining the website after it's been made.

It is now time to talk about how it's going to be developed. This is step three in the workflow or the framework here. This decision needs to consider your unique situation. This includes budget. This includes available time, technical knowledge, design complexities, design capabilities.

Are you really, really artistic? Are you not? Long-term maintenance requirements. Notice how we haven't talked about anything. We haven't talked about React. We haven't talked about Svelte. We haven't talked about any of this stuff. These are crucial things you need to figure out here. So I have a few options here.

You have option A, build it yourself. That's fantastic. There's some advantages to that. Potentially lower upfront costs. You have control over the process. You can nitpick yourself to death. Go ahead. Although if you're a perfectionist, that could be bad, and I'm a little bit of a perfectionist, and it's bad.

So there's that. [00:36:00] opportunity to learn new skills. You're gonna learn new skills. I'll mess around with the Canva website builder. Ah, I'll mess around with WordPress instead. I'll do this, I'll try that. Learning new skills, and it's also easier to make changes independently. You can wake up at four in the morning and do 'em if you really wanted to.

It's up to you. It's up to you and your schedule and your life. You don't have to worry about contacting somebody and saying, "Oh, I accidentally used up all my hour allotment at my developer this month." But the problem here is there is a learning curve, and your actual craft, your business is generally not going to be web development.

There's many other businesses out there, and the thing is, you already might have a learning curve or enough on your plate as it is. So you might not have the time for that learning curve. You might not have the time to invest. So there's that. There's also potential design and usability issues. You might not know how to make a, a good-looking logo.

You might not know how to do good art or things like this, and, and I don't mean art like you're gonna be painting, you know, amazing, [00:37:00] immaculate pictures and doing amazing illustrations, but you do need to know some certain things, such as good contrast on certain pages, contrast between readable text and, say, a background for accessibility, things like that.

You're gonna probably overlook some technical issues, and if you're worried about that, well, you're probably gonna do it 'cause you're not even gonna know what to Google or what to look for. And then if you run into a problem, troubleshooting can become difficult because you might not even know what prompt, question, or Google search you're supposed to be typing in.

Website doesn't load. Well, that's great. For what reason?

Mikhail: I think another point to that, like you might not even know there is a problem. You might be thinking everything's fine, but your SEO's janked. Your URL is not secure, right? All, all your metadata is wrong, so it's sending people to the wrong thing. You're not showing up in these searches. How, how would you know that unless you understand at least to, to some degree those concepts?

Matt: You wouldn't

Mikhail: mean? So you, you, you might just be thinking everything's okay, but it's not, [00:38:00] so you're not even asking, not even asking questions because you think everything's okay. So it's just, it's important to understand where you're coming at this from if you have the knowledge to understand something is wrong or not. if you think that AI can do everything, great, you still have to be the one that kind of prompts it to do it, and if you don't know when to prompt it, it's gonna be tough

Matt: Well, also, if you are in, I'll call it an SEO battle with somebody, and the other person has really crossed the T's and dot their I's, maybe you don't have a major issue, but then how do you beat them? And asking an SEO-- asking for SEO advice from a bot is fantastic, it's great, whatever, but it is, it is parroting stuff that has already been done.

It is parroting stuff that is usually the middle-of-the-road advice, or very, very common advice. Well, if you were a top dog and you followed that, that, that advice, someone else showed up and took it from you, they did something more innovative. Maybe they did prompt a bot to [00:39:00] give them more innovative advice, or maybe they went to a different product.

You're using ChatGPT, they went to Claude, whatever, who cares? The thing is, you don't even know to ask those questions, and you're just gonna be basically hitting your head off the, the, the ground. Like, I have a client that when ChatGPT first launched, he became obsessed with ChatGPT, and he became obsessed with AI.

Everything that came out of that bot's mouth, figuratively speaking, he thought was this amazing truth that was unshakable. And I would tell him, "This, this bot is parroting things. It's acting on your prompts. Your prompts are imperfect. I'm imperfect too, so yeah, maybe it found an issue on your site, and I'm totally, absolutely happy to fix that.

If I didn't, if I missed a, missed something or," 'cause this is an ongoing client, "If I need to fix something or I missed a T that I didn't cross or some- absolutely. But there's some stuff that this bot is telling us to do that is wrong. It is wrong for the strategy we have in place. [00:40:00] You have to either learn to identify that, that the context that this bot has is not complete, or you need to start giving the bot more context to try to get more complete answers, or you need to talk to me about it."

But the problem was is he was taking this bot at face value and was trying to implement everything this bot was asking and unfortunately, it, it just wasn't a good result. We were doing things completely counterintuitive. We would go toward-- We'd fork in the road, we'd choose the left direction, we go all the way to the left direction, about to get the reward, turn back around, go up part of the way B, oh, back around, and then go up the middle somehow through, like a random side path that we didn't see before.

Not good. So you need to-- Even having AI on your side, you need to know how to direct the thing. You need to know how to work with it, and having professional knowledge beyond that of the bot is very, very [00:41:00] crucial, especially when you're competing with other humans. You're competing with other people that are trying to do SEO So what's the next thing here?

Option B, hire a professional, of course. And this could be different types of professionals. You could just hire a web designer if you're, if you don't wanna do the web design. You could hire a freelance web developer and get them to do the whole thing. Same goes with a development agency. Go ahead. You could get a full-service digital agency.

You could decide after doing step one and step two, "The heck with this. I don't wanna do this. I've already spent all this time putting it together. I've already thought this all through. I do not wanna do this. I wanna do my welding, my landscaping, my this, my that. I'm gonna hand this over." Good. Hand it over to them.

Makes sense. You made a very good, informed decision for yourself, right? 'Cause the advantage here is you're probably gonna get faster delivery than if you did it. You have your professional expertise that's there, and you're going to... 'Cause step four is getting more technical, which we'll get into in a second, but you're gonna get guidance on platform [00:42:00] selection.

You're gonna be able to have a conversation with this professional, and you're gonna be able to say, effectively, "I did step one," and you say what, what it is you wanted on your website and what's your website for. Then step two, you're gonna say, "Okay, this is what... This is my mainta- maintenance schedule.

This is how much I wanna maintain it. This is the things I'm gonna maintain." You can have these conversations with these agencies, and then they will come up with a platform. They will say, "Okay, maybe you should use WordPress. Uh, you know what? Maybe not. Maybe we'll use this. Uh, you know, it could be a static website.

Kinda sounds like you're gonna update your hours once every two years. Let's just have a static website." You can absolutely have that conversation, and they will help you, a professional will help you make that decision and go through the pros and cons oftentimes with each of those decisions. 'Cause they may have a couple of ideas.

Heck, it could even, it could even hinge on your own experience. "I have a ton of experience with WordPress from a prior job." Okay, maybe we'll do that then. Let's go with WordPress so that there's less friction in getting you spun up. Clearly, you don't have a lot of time. You're hiring a web dev agency. You don't have a lot of time for yourself, so let's make this as [00:43:00] quick and as painless for you as possible.

But of course, with option B, there are some disadvantages. You're gonna be paying more upfront costs. There's gonna be a little bit of pain always, right? Finding the right professional can be challenging. You might go to a freelance web developer and find out that they just have too much on their plate, and they're not working fast enough for you, so it's gonna be hard to find someone that is a right fit for you.

There's potential ongoing costs. I mean, there's always gonna be hosting costs and things like that. Short of the odd website, you could maybe find free hosting, but at the very least, you're gonna be paying for a domain name, unless you're gonna use some free subdomain thing, which don't do that. And obviously, you're depending on somebody else.

You can't just wake up at 4:00 in the morning and send an email and that thing will be done, or you reach for a CMS and that thing will be done. You have to reach for a professional, unless they've installed the CMS for you, of course. So you have to... You've given up some control over when those updates can be done because you have to operate under their schedule 'cause they're likely having more than just you as a client

Mikhail: Yep. I have a hot take here. [00:44:00] I, I think if you're serious about your webs- or if you're serious about your business and you're serious about your website, which you should be if you're serious about your business, I don't think there are any other options other than finding the right agency, which, which is a pain and can take time, and you should ask for referrals, like, ask around.

You know, you should get someone that you can trust. You know what I mean? Not the first thing that you see in the phone book. You know, fuck the phone book, but like, you know, you know what I mean. Like, not the first thing you find. Find

Matt: No,

Mikhail: you can trust

Matt: I would want to say one, one quick thing though. You work with small businesses, especially in a small town, people are reaching for the phone book. Some people are. Some people are. It's, I mean, it is a niche, but some people are definitely doing it

Mikhail: Yeah, they're still doing it. Yeah, there's still, there's still, you know, Joe in, you know, bumfuck nowhere that's reaching for the phone book. But like, okay, so if you're serious about your business, there's no hybrid approach in my opinion. There's no do it yourself in my opinion. You find someone that has built a successful, just website, but internet presence [00:45:00] for a business in your niche, whether it be plumbing, whatever. You go with them because they have proof that they've done that, and you give them full control That, in my opinion, that- that's the only advice that I would have here. If you're a- if you're someone listening to this that's actually looking for advice on like, "Oh, I, I have a small business and I need help here," find a partner that will make it so that you have 10 times more leads because they've already done it for someone else in your industry. Not easy. not saying that's easy, but I'm saying that those kinds of relationships and those kinds of partnerships that you find are gonna be 10 times more worth it than you dicking around with designing something and giving it to some random freel- freelancer to build, or you dicking around with Wix and being like, "Okay, I have a business card website up.

Great." Like, okay, I, you know, done a checkbox. If you're serious about your business, this is if you're serious, you need to do the right thing and get [00:46:00] as much streamlined help as you can in this specific instance. Because just talked about the very high level things that need to be done for a website, the very high level.

We did not mention anything in depth. There is 100 times more things that need to be done to build a successful lead generation website that actually converts to paid customers, right? 100 times more things. And doing it with someone or for, by yourself with no in, no information and no, you know, just in the sh- shooting in the dark without any way to like analyze if your approach is working or not, like it's not worth it.

Like you're, you're wasting your time. You might get something up there. You might get a couple clients, great, if you go with someone that knows what they're doing, you might get 10X the clients. You might be able to expand next year. You might be able to hire another, another five people. Like, it's a different mindset here.

So I think it's good to have an idea of all of these options, right? Especially if you're listening to this as a developer and you're trying to pitch someone different [00:47:00] options, right? Like there's, there is some of that to this. But really what every developer, whatever agency, what, what we like as Matt and I are, are pitching at this point is success.

we're pitching you more money in the door, gonna pay us some of that money upfront, and there's a risk to that. gonna pay us some of that money, but we're going to do everything in our power because A, B, and C, like we have this, we have this proof that we can do it before, to get you more money into your business. So it should-- I don't wanna hear your design criticisms. Like I, I don't... Like all of that stuff is, is useless in my opinion from a, from a, from a product owner. Again, I said this was gonna be a hot take. It's a hot take. All of the little nitpicks of a website, oh, this button should be over here, I don't wanna hear it I'm doing it this way because it's gonna get more people into your business.

Is that what you want? Yes? Great. That's it, right? Like, I know what I'm doing here. This is how we should do it. Now, again, I know, uh, it's, that doesn't vibe with everyone. I [00:48:00] understand that some people like to have a little bit of control. Okay, I get it. at the end of the day, your goal is to get more business at the, in the door and to establish trust in the community. That's how you do it. Find the right partner

Matt: Especially if you want a hands-off approach, we've talked to other web dev agencies that have absolutely told us that they don't let the client get bogged down in design decisions. That was a, a big part of your hot take there, and 100% right. I've had people that are so picky about the alignment of text that I've created buttons in my CMS that just, like, switch it to, oh, they want it left today, oh, they want it centered, oh, they want it right.

These people are very few and far between. I wanna be clear. This isn't my day-to-day. But it's, there are, there are some people that are like that. Why is this this way? We need to move this slightly to the left. No one's gonna come to your website and go, "This is three pixels over to the right. I'm leaving."

Unless it's unreadable, point out mistakes. There's lots and lots of stuff to do with [00:49:00] websites. If you're having a problem on your phone, maybe I made a mistake in one of the responsive viewpoints and this thing needs to be visible. Yeah, absolutely tell me that. If I missed something, I missed something, I own it, I'll go fix it.

That's it, 100%. it's, it is a good point, Mike, 'cause some people will get super, super, super in... It's usually the design. They usually don't care about the tech stuff. They usually care about the design, and they get super into it, and it just gets out of control. Even to some extent with the CMS, it's a little less...

It, it's more of a utilitarian issue, but people get really stuck. I don't like this image uploader. I don't like this. I'm, I don't like that. So that's why I spend a lot of time making my CMS very easy to use. You wanted to type in a testimonial, you log in, you click Testimonial, you fill these two fields in.

It'll stop you from entering too many characters. It'll stop you from accidentally forgetting a field. You press Publish, it goes live. You [00:50:00] wanna make it a draft 'cause you want Bill to look at it? Bill already has an account. Fantastic. Make it a draft. Tell Bill to look at it. He can look at it. He can publish it.

Done. It's meant to be easy, and I, I think you're right. If you, if you're a person that's just looking to boost their online presence, having a professional help you absolutely is something that you should do. Have, have them c- go in and do that stuff. Don't worry about something's right aligned but doesn't have three, three more pixels of padding.

Do you care about getting more plumbing clients if you're running a plumbing business, or do you care about the three pixels of alignment?

Mikhail: Focus on what you're good at, right? if you're good at plumbing and you're good at managing plumbers, focus on that and find a partner. Again, this is not hiring a freelancer, this is not hiring... Find a partner that you trust to do the things that they are the best at. you, you have to that trust.

Like, you have to vet them. You have to, again, get referrals. [00:51:00] deep into that. Make sure that you can trust them. But once you establish that trust, once you know you can trust them, then you have to let them have free rein because that's the only way you're gonna have real success. Now, you, you know, again, it's,

Matt: Well, they, they would be a freelancer too, I w- I would like to say. Like they, like you're saying not necessarily a freelancer, they would be a freelancer or like a full service agency or, or something. Like they would be that

Mikhail: exactly. But, but what I'm trying to say is it's not like some part-time freelancer that's just building you a website and leaving. You know

Matt: Oh, yes. That's a good point

Mikhail: I'm trying to get away from. It's, it's someone that's going to get you more leads into your business. It's someone that understands holistically what you, what needs to be done to go from zero to 10 to 100, and how to, how to track that and how to get that in. And it's not just a website at that point. It's Google My Business, it's, you know, ads, it's the, the, the website is kind of almost a small part of it.

Matt: Yeah

Mikhail: So it's difficult to build that level of trust, I wanna make that very clear, because people have been burned on [00:52:00] websites before.

Like, you talk to, I, I, you know, you talk 10 agency owners, ev- eight of them are gonna have a story about how their web guy screwed them. That's how, that's how our industry is. So it's difficult to build that level of trust, but if you can find someone that you can trust, them have the free reins.

Matt: We've done so many repair jobs on those too. We've done a ton of repair jobs, on people who have been like, "Man, like this person moved me from host to host and like none of my content loads, it just loads the lorem ipsum." It's like, oh great, you know, we gotta go in and fix it for them. Which, which I'm happy to do, but it's like, you know, why, why leave them in that state?

Like that's not... Le- left them in that state and then literally just left, took off, ghosted them. It's like why? Just, just fix the problem. Fix the problem and that's it. It's all you needed to do and that would've saved your own reputation. But, well we've mentioned option A, we've mentioned option B. DIY option B is hire a professional.

You can do an option C. Option C is definitely a hybrid. Tons of niches out there, tons of websites out there, tons of businesses out there. You might be a [00:53:00] person that goes, "Hey, uh, I'm gonna hire a professional designer and I'm gonna do everything else 'cause I'm a tech person. I'm going to do the design 'cause I'm an art person, and someone else is gonna do the development.

I'm going to build all the website scaffolding and everything else with AI, and then I'm gonna find a partner," as Mike says, "and I'm gonna have them manage it, fix it up," yada yada. Even if that site is just kept private for the entire time and then you just go, "Hey, this is the site I came up with. What do you think?"

They'll come in, they'll rip it into different pieces and change things depending on the SEO goals you have and things like that, and there you go. So there's a hybrid approach. and the hybrid approach could save you money, it could also cost you money, I wanna be clear, 'cause if they have to spend a lot of time fixing stuff.

But if you want a lot of control over the design, if you want a lot of control over the tech for some reason, the hybrid approach does work. Absolutely. I mean a hybrid approach here is sometimes I, I absolutely can fix my own electronics. Sometimes I go to a professional 'cause I just do not have time to fix it.

That's fine. Get it [00:54:00] done. I'm effectively at that point getting two things done at once. I'm, someone else is, someone is fixing my computer while I'm working on my laptop as an example

Moving on to the fourth step. The fourth and weirdly very important, but also potentially, like, least important step as well, 'cause today you can kind of move on a dime, and it is the actual tech. How will this project, how will this website actually be built? This is where a lot of people start. This is why I keep mentioning the importance of the first three steps.

This is where most people start. "Ah, where do I... I need a website. All right, cool. Do I go to Wix? Do I go to Squarespace? Do I go to Webflow? Do I make it custom? Where do I go? Who do I, who do I call for that?" They haven't even decided what's supposed to be on their website. They haven't decided any of this stuff.

They haven't even discussed it. And I think this is a good point to mention something here, is that if you do decide to hire a professional, they can do all four of these steps in one way or another for you. If you really are unsure or do not have the time to do these steps [00:55:00] yourself, you can absolutely go, "I don't know if I need a website.

Let me call one of these agencies." Now, here's the thing. Those agencies are obviously gonna try to sell you on a website. Anyway any agency would. Of course they are, because you've approached them. But if you really, really do need help, sometimes the professional help is just the way to, the way it goes.

So here's the thing. You have a bunch of options here. What approach or what technology makes the most sense, okay? If you're, if you're deciding this yourself and you're like, "Okay, I'm gonna look through all these options. I'm not gonna go to a professional. They're not gonna help me do this. Let me, look at these approaches myself," I have a few approaches here.

The first one is option A or approach A, website builders, something like a Wix or a Squarespace. These are great for small businesses. They're great for portfolio websites. they're great for users that don't wanna do any coding. These are great no-coding tools. They're big tools too, so there's... They're gonna have integrations into a bunch of things, so if you do have, like, a Mailchimp or a, a newsletter integration that you want, [00:56:00] chances are these, these sites will have it And the same thing goes with, Shopify.

Shopify if you're going e- if you're going heavy e-commerce, but there are e-commerce solutions within Wix and Squarespace as well if you wanna do that. But the point here is that they're relatively approachable, that you can go in, no code, get some things done. Hosting is usually included with these things.

There's visual editing tools. You're clicking, you're dragging, you're changing content boxes, you're using templates for things, and they manage all the, all the other junk. You don't have to worry about server performance and things. They do that. But here's the thing. Because they're managing it, there's gonna be limitations.

There's gonna be things that you wanna do that maybe they didn't prepare because they're preparing for a general audience, and so you might run into some limitations based upon your needs or wants. You're gonna have recurring subscription costs, although that's almost always the case, as we've already mentioned, and you may have potential difficulties migrating elsewhere, although it's not impossible or, you [00:57:00] know, crazy or anything like that.

So if you really wanna DIY it, you're not technical, starting here is fine. Starting on Wix or Squarespace is fine. The thing here to note in step four is this is potentially not your forever home. It, it might be. Obviously, don't make it your one night, "Oh, I'm gonna be on Wix one night, and then I'm gonna go to Squarespace the next night, then I'll go to Webflow the next..."

No, we're not doing that. But these, this does not have to be your forever home. You know, get started. Don't let f- don't let perfectionism be the enemy of this step. Try to get started. You've already done step one through three. You've already prepared a bunch. Let's see if we can get something going here.

What's, what's option B? visual development platforms. There's several out there. The one I'm most familiar with is Webflow. These are great for design-focused websites. These are great for marketing websites. These are great for small to medium businesses. This is great for a collection of landing pages.

I've seen people who quite literally just use Webflow, and they direct a subdomain to Webflow, and they just rapidly make landing pages on there because they [00:58:00] do a lot of ads. Some people do a heck of a lot of ads, so there you go. There's a bunch of design flexibility here. You're not really using templates.

You can if you want, but you're not really using templates. There's a built-in visual development environment that's pretty advanced but also pretty accessible for the level of how advanced it is. And then they also have website features, too, like CMS, like managed hosting. So they, they do all the hosting for...

They do the hosting stuff for you, right? You don't have to write really any custom code, but you can if you want to extend the capabilities. And what I like about Webflow is for my customers that are more design centric- It's instant feedback. I've been on the phone with them.

"Can you change this?" "Yep." "Can you change that?" And sometimes it is those little changes that Mike was saying that don't really make a difference. Some people are really design-focused. You're never gonna get that away from them, and that's fine. On the phone, one hour, let's do 50 changes, rapid fire, do this, do that, do this, move this, move that, move this.

Boom, boom, boom, and they can see it instantly. Publish, publish, publish. "Oh, that [00:59:00] looks great. Okay, let's do that. You know what? Let's change that back." Great. Now we're checking off these things quickly.

We're getting through their design obsession by using this type of system, a visual development platform. And there's other ones out there, too, but Webflow is the one I'm most familiar with, so that's the one I'm, you know, gonna comment on.

Here's the thing, though. Because they are design systems that are very capable, they do have a learning curve. Wix and Squarespace have a learning curve, too, but not as strict, not as steep There's subscription costs involved. I often call Webflow the Apple of websites because it is kind of a gated community.

Yes, they have tons of plug-ins and add-ons now, but still, it's a relatively gated community. They deal with all the hosting stuff. They tell you kinda like, "This is what... this, this is how this works, this is how that works, this is how our CMS works" kinda thing, and you just kinda have to go with it. But yes, there are some flexible pieces, but usually with code.

And the thing is, if you really want some advanced integrations set up, sometimes you do need to mess with some code. Oftentimes [01:00:00] it's just copy/paste. But if you really don't know how to do that, if you're really, really hesitant, then this solution might not be for you. Approach C would be a content management system, something like a WordPress, which is obviously a CMS, but also a development platform.

So WordPress is a blogging platform first. It's a, CMS, a content management system first. I did mention that something like Webflow does have a CMS, and obviously you can update your content on Squarespace or whatever, but this is a CMS first. That's what approach C is all about. And this is best for people that really need a lot of content that goes in and out of the website a bunch.

Blog posts, you're posting news, things like that, right? This is great for business websites. This is great for websites that require extendability. You can take a WordPress site, for example, spin it all up, get it all done, and just use a template, and then in five years be like, "I wanna keep all my content, but I need a page builder."

There's page builders for WordPress. Go and install a page builder for WordPress, use that same [01:01:00] information. Even if you have to rebase, if you have to literally take the information out of one WordPress and import it into another one, there's tons of import/export solutions out there. Like, this is meant for people that are slingin' data, slingin' content like crazy, images, text, all over the place, tons of pages.

If you, if you have 100 pages on your website, you're probably gonna go with something like a WordPress. And there's a ton of other options out there, of, of course. There's some great advantages to WordPress. Large ecosystem, extensive plug-in, plug-in availability, flexible content management, broader development support, self-hosting options, or there's also managed hosting options as well.

Problems are, of course, because it's so extendable, you might have some compatibility issues between plug-ins that you need. Because you're self-hosting, there may be some security issues. Because WordPress is so popular, there may be some security issues 'cause people are constantly trying to break in.

You have to make some decisions here. You have to make some hosting decisions on whether or not you want self or non-self-hosted. That's up, completely up to you. And [01:02:00] here's the thing: because it, it's potentially self-hosted and because it's so extensible, extendable and changeable, you might run into some performance issues because you may have chosen a bad host, you may have chosen some bad technical decisions, and it can make your WordPress very, very slow And not last, was last maybe a couple years ago, but not last, custom development.

I'll just touch on it 'cause it's, it's the way it is. You code your website up. You choose a HTML, CSS, JavaScript, you choose a stack, you choose your React, you choose your Next.js' you choose your SvelteKits, you choose that vanilla like I just mentioned, the HTML, CSS, JS. You make... You just make it from nothing, basically.

You code it up. And if you do not know how to do that, then you should get a professional to help you. But it's not the last option anymore because you have AI-assisted web development now too. And AI assistance can help you generate a full website, of course. There's prompt-based tools. It feels like a no-code [01:03:00] experience, but the thing is, is that the AI can, can generate that code, and it can generate that custom code.

Now, custom code is great for things like web apps and very, very custom solutions, and AI is great for making that complex stuff seem like a no-code tool. It's not. AI is great for rapid prototyping and, simple projects and things, and it can be really great for really good projects if you know what you're doing.

But the thing is, is you are going in completely blind because you're prompting this AI, and generally speaking, they are general purpose AIs. So if you just go into Codex or you just go into ChatGPT or you go into Claude Code, somebody's making a Android app, someone's making a Windows app, someone's making, just a research report.

These are general purpose AIs. And so the problem there is that you are going in completely blind in the same way that you would be with something like Squarespace, but Squarespace, that staff is there to allow you to make websites. They have made their whole platform around the idea of [01:04:00] making websites, whereas AI, you are directing it.

Like, you aren't directing the Squarespace staff. You are directing the AI, and if you don't know how to direct it, you could seriously make some mistakes here. But those are the options that I have listed here

Mikhail: I have another hot take on this one. I think all of these options should be done with approach E. Let me explain. If you're gonna use Wix, you're gonna use W-Squarespace, they have some AI built into it, so you're already probably going to be doing AI-assisted website development inside of Squarespace today. If you, if you're gonna use Webflow, it's the same thing. It has AI built into it. But not only that, you could use anything like Codex or Claude Code to help you, do the actual development inside the browser. 'Cause Claude Code can control your browser like it's no tomorrow. it can just do any, any edits for you, anything that you want inside of [01:05:00] any of the applications that you choose. WordPress is a perfect example. WordPress is just code. There's not an app in-built on top of it, it's just PHP, right? And it, and, and then if, if it's not PHP, it's a, a page builder if you have to maintain something. again, you're probably today going to be using AI-assisted development to even do anything inside of WordPress in my opinion as well. WordPress is something that AI knows extremely well. It's just PHP. It has so much training data on it. It can do anything from zero to one. Now, yes, you need to know what you're, what you're prompting, but the same thing if you were to spin up in Webflow from zero to one, you would need to know how to spin up in zero to one.

With AI assisting, assistance, you're gonna be able to do that much faster, and much safer, by the way, because AI is going to know things on top of what you ask it. So if you ask it to make you a, a page, it's gonna know that, hey, I probably need to put SEO here. I probably need to do this. [01:06:00] I'm talking the top AIs right now, like if you're

I'm talking Opus-level AIs, it's on a different level than it was, three months ago, six months ago, where you did have to steer it a lot more. Steering is a lot less required nowadays, so as long as you're able to generally ask it a question o- on a we- on a webpage, it should be able to do the things around it that make it at least somewhat usable, right?

It might not be perfect if you don't know what you're talking about. It's probably not gonna be perfect, but it'll be better than you doing it yourself from zero to one, you have infinite time. Then obviously you learn it so in-depth that you become the expert. But if you're running a business and this is the thing you do on the side, you're not gonna have infinite time.

So of which one you choose, approach A to, you know, B, C, D, in my opinion, 2026 right now, November, you have to be doing it with approach E. If you're doing it manually, again, this is the hot take, you're doing it wrong

Matt: I like your hot take to an extent. I will say this [01:07:00] though, is that we've built websites in such a similar manner, not similar looking, but in such a similar manner with WordPress for small businesses specifically, so frequently, and I've maintained those websites and things like that, that I'm so fast that I have barely used AI inside of WordPress itself.

I've used it for help with some things like compatibility as, and things like this. Like, there's been some sort of, like, chatting around WordPress, of course, naturally with the job. But the thing is, is I believe that you can just connect via an MCP server, I believe. You can just connect, AI to... I haven't tried this.

Like, obviously there's people out there that know this, I just haven't done this yet. But I think with WordPress 7 and then onwards, there's an MCP server. You can just connect it, connect the AI to it, and then it of course can do things on your behalf. You know, change things around or what have you. And you're right, obviously there's a ton of documentation, blog posts, comments, et cetera out there, out in the, the wild that, [01:08:00] about, that are about WordPress, so it is...

AIs are very informed about WordPress, so they'd probably be able to help you a lot. But I'm so fast that I'm just, it's like I'm not even gonna bother prompting. I'm just gonna do it, 'cause I've been doing it for so long, and then anything that I am new to, or if a plugin updated and I don't know where it is, then I ask it for help.

So I agree. Oh, no, I'm just talking about WordPress. I agree wh- I agree with what you're saying, though. AI assistance can help you in any of these approaches. Obviously approach E is largely, though, the AI doing other majority of the work, and then usually it's either custom co- It can be anything, right?

Custom code, it could help you spin up a WordPress that could do this and that. Or you could just choose WordPress, do, do, do it partially manually, and then start to ask AI for help. But I

Mikhail: my hot take is you shouldn't do that. Even if you are an expert WordPress developer. That's my h- again, it's my hot take because I've, done this competition already. [01:09:00] I've done the manual versus, versus, AI-assisted, and I have lost. Even, even on stuff that I was extremely well-versed in, at this point I have lost.

Now, not every, iteration I've lost. Sometime, you know, if it, if it's literally flipping a switch, won. But what I've

Matt: Yeah

Mikhail: it and the more I've done with it, it does things outside of the realm that I would've done, that again, I'm learning how it's doing things and that, an expert from across the world is doing things essentially. And so it's extended my skills and my, the abilities that I could've done, regardless of how fast it is. It's not always about speed to me as well. if it is just flipping a switch, sometimes I will go and just ask it to do that, and then work on something else in parallel potentially. But like, it could come back to me and be like, "Hey, I flipped a switch, but I also went to, in, into this settings panel and did this, this, and this because you didn't have that set up."

Like, it, it's done that before. Whether that's right or not, or not, I have to question it, but [01:10:00] sometimes it's right and I'm like, "Oh, I would've never done that." So at this point in time, the top-tier models, again, are gonna be better than most people at these things. And you, an expert with a top-tier model, being able to q- you know, it and steer it correctly, is going to make it even better than it could've been with like an amateur obviously.

So

Matt: Yeah

Mikhail: I'm not saying you have to do it, obviously. This is the hot take part.

Matt: No, I know. I get, I, I get that

Mikhail: to fully approach E for all development, regardless if it's WordPress, regardless if it's custom code, regardless if it's going, literally going into a Wix whatever. I, I'll tell my browser, control agent to do the things that I need it to do,

Matt: I understand what you're saying

Mikhail: and stuff like that.

So like, th- that's, that's it. I, and I understand you can do it fast. I totally get that. You can... Like, there's a lot of things you can do fast. But I would [01:11:00] d- I would challenge you and be like, "Hey, just try it the other way, and really give it a shot. Don't just try it and stop. g- like, go down the path of like, okay, just use the top-end Claude code or the top-end Codex model and do the same things you would do that, but with it instead,

Matt: I'm definitely gonna try it with WordPress. I've just... Right, lately I've been literally, like, patching PHP, and then I've been doing just regular content update actually for some people, so I haven't really been building in WordPress for the last, like, couple weeks, I guess. But, hmm. I, I think I need to try it.

I think I need to try it. But I- when it comes to AI stuff, and, like, this is definitely off topic now, but we're at the near the end of the episode anyway. But when it comes to AI stuff, the thing that I am kind of adopting is I like to work alongside the AI because we're both a source of, I'll lose- use the term loosely, [01:12:00] intelligence, if that makes sense.

Like, obviously humans have intelligence. People argue AI isn't intelligent. I'm not gonna get into the, you know, whatever. But, uh, it's two... It, it is capable. It's two sources of capability. I'm capable and it's capable, so I work alongside it. There's a better way to put it

Mikhail: It's, like again, there's no right, right or wrong here. I'm just, I'm just telling you like how my hot take

Matt: No, no, I, I know, I know. It's just an interesting,

Mikhail: Yeah.

Matt: uh, philosophy, I suppose. But, but I think that's it. That's the four-step framework, four-step procedure, if you will, four-step workflow, ooh, uh, if you will, of how to make a website. Obviously, I'll have a bit of a different title for the episode than that, hopefully, or probably anyway.

But the idea here is to sort of set you up for success the best way that I personally know how, and a lot of it is soft skills, a lot of it's business decisions, and a lot of it is not technical decisions, even though [01:13:00] that's oftentimes where people start, which I think is a huge mistake. Having made tons of websites over the years, I, I sincerely think it is a mistake.

But that's it. Let us know what you think If you think that this is a good idea, bad idea, let us know in the Spotify comments. Let us know in the comment section of any app that you're using. Let us know in our social medias, all that stuff. Let us know because we wanna read your thoughts, because a lot of this stuff is definitely gonna be different depending on your own niche, your thoughts, your expertise, et cetera, et cetera.

But that's it. Thank you for tuning into this episode. Remember that we are on Patreon if you wanna support episodes like this, and that can be done via patreon.com/htmlallthethings, and many thanks, thanks to our $3 tier patrons, Tim from The Web Hacker on thewebhacker.com, Magnus from YesWeb via yesweb.se, and Syntaxify from the HTML All The Things Discord server.

[01:14:00] And remember that we have a Scrimba discount link. If you wanna use our link, it'll be in the RSS description and in the show notes on htmlallthethings.com. You get up to 20% off that Scrimba Pro plan. Use that interactive media player code editor to edit code while the instructor is teaching it. Pause the lesson, play with the code, press play, and have the lesson pick up right from where you were.

Go and check that out. They've also been experimenting with a bunch of other features, so if you go and check out, go and check out the Scrimba website, go and check out any of their social medias. They have a whole bunch of new features always kind of coming out. They're always playing with stuff and talking about it, so it's really interesting to see.

And remember that we have a contributing author, and that is Michael LaRocca. He is the author of Self-Taught: The X Generation blog at selftaughttxg.com. And that's it. Feel free to leave a comment or review on the platform you're listening to this on. And we are signing off