Michael Youngblood's PortfolioMichael Youngblood
This Codebase Code Repo for Michael-Youngblood.com

2025 Project Brainstorm

2025 Project Brainstorm

This brainstorming session aims to identify features and products that will be divided between AlienDev.com and the SEO Tools Subdomain. Some of these features might be relocated to Michael-Youngblood.com or different subdomains if deemed necessary.

The Brainstorm

  • SEO Spider – a spider that crawls predetermined websites and configurations to collect information

  • SEO Calendar – Compare crawls to determine changes from one date to the next, identifying these changes on a calendar / timeline. Search and extraction functions to expand the uses of the spider.

  • Site Health – Reports for technical SEO issues, broken links, Site Speed, authority scores, etc.

  • Blog – I’m not sure I want a second site with a second blog, but I’ll put it on the list.

  • SEO, SEM, and CRO Experiment writeups

  • Keyword Research

  • Pull data from Google Search and Bing Search Consoles.

  • Google analytics data

  • Backlink profiles, toxic backlink reports.

  • Organization, and account management. Individual account, vs org. Conversions possible. Users should be able to self manage as much as possible.

  • MFA – secure your account with multi factor authentication

  • Invoices and billing notices should be sent to a billing contact, if one is available

  • Local Software version of crawler

  • Compliance check? An automated way to check if a site is compliant with CCPA, GDPR, TCP, and even APA accessibility.

  • A MUD in the console

  • System status page – various things, users need to know if the service is up or if the issue is on their side.

  • Request for research / blog

  • Twitch link / integration – weekly UX and SEO Discussions?

  • What I’m playing now? Maybe to do some game reviews to add some content to my personal blog? From a UX and developer point of view.

  • Make simple games and discuss code development patterns

  • Discuss different product manager and software engineering documents? Make some samples as well.

  • Software selection documents and discussions. These do not get utilized as much as they should these days. It’s aways about preference, not what’s best.

  • Why make “memos” for everything you do.

  • Article about knowing your systems and ensuring internal stuff stays internal.

  • Make a new memo and spec system. Except, in a good language for the job, like react & next. Should have versioning and all that shit as well. These should have categories and departments as well. I’m a little torn, I think they should probably use markdown, and allow versioning right on it, as opposed to word like Complete Solar had, will discuss later.

  • Requirements documents.

  • Template database.

  • SEO, SEM, and CRO Reports, Documentation, and Projects.

  • User Experience Reports, Documentation, and Projects.

  • Python projects

  • Choosing a hosting provider or system architecture suite article