Problem Solving with AI

 When I decided to move Heartland Genealogy from WordPress to Blogger, I thought the biggest challenge would be moving the content. Instead, I've received an unexpected education in DNS records, custom domains, HTTPS certificates, RSS feeds, featured images, redirects, and social media previews.

And, as has happened several times during this move, ChatGPT has served as my troubleshooting partner.

The Custom Domain Adventure

One of my goals was to use my Heartland Genealogy domain with Blogger. I already owned heartlandgenealogy.org, and I wanted readers to reach the Blogger site through www.heartlandgenealogy.org rather than a Blogspot address.

That sounded simple.

It wasn't.

Blogger provided the CNAME records that needed to be added to my DNS settings. After making those changes, there was the inevitable waiting period while the new DNS information propagated.

Then came the questions.

Was the CNAME correct?

Did I need to turn on Redirect domain in Blogger?

Why did Blogger report that the HTTPS status was "unknown"—and, at one point, "failed"?

Was a 30-minute TTL causing a problem?

ChatGPT helped me work through those questions one at a time. We checked the Blogger settings and discussed what the various DNS records were doing rather than randomly changing things in hopes of making the site work.

Eventually, a ping to www.heartlandgenealogy.org worked, and, more importantly, the site opened in Chrome.

Success!

But solving the domain problem didn't mean I was finished troubleshooting.

Then There Were the Social Media Previews

As I started scheduling posts in Meta Business Suite, I encountered another issue. Facebook wasn't always displaying the featured image I expected.

Sometimes it pulled the correct image. Other times it pulled my picture or even a generic Google "G."

That led to another round of questions about how Facebook creates a link preview and what happens when I schedule a social media post before the Blogger post itself has been published.

That timing matters.

If Facebook tries to retrieve information from a URL before the Blogger post is publicly available, there isn't necessarily a featured image for Facebook to find. Attaching an image manually can solve the visual problem, but it doesn't change what information Facebook retrieves from the webpage for its link preview.

That helped explain some of the inconsistent results I was seeing.

And Then Feedly Entered the Picture

RSS was already part of my blogging workflow because I use Feedly to follow genealogy blogs. Thus, I also care about how Heartland Genealogy appears to people who follow it with a feed reader.

During the WordPress-to-Blogger transition, I had already encountered missing featured images in Feedly when changes to my WordPress configuration affected the image URLs in the feed.

Now I needed to understand how Blogger handled feeds.

That led me back to ChatGPT with another question: What is the difference between Blogger's Full and Custom feed settings?

I learned that Full sends the complete post through the feed. A reader using Feedly may be able to read the entire article without ever visiting the blog.

Custom, on the other hand, isn't simply another version of the feed. It opens additional controls so I can decide how Blogger handles the posts feed and the comment feeds separately.

Then I noticed another option: Until Jump Break.

Another question for ChatGPT!

What's a Jump Break?

A Blogger Jump Break is a marker placed within a post. Everything above that marker can serve as an introduction or preview, while the remainder is available after the reader continues to the full post.

When Until Jump Break is selected for the feed, Blogger sends the portion of the post above that marker to the RSS feed.

That gives the blogger more control than an automatically shortened feed. Instead of Blogger deciding how much of the beginning of a post to include, I can decide exactly where that break occurs.

Of course, that also means consistently adding jump breaks to posts.

For now, I'm leaning toward making the complete posts available in my feed. As a Feedly user myself, I appreciate being able to read posts there. However, I now understand the alternatives and can make an informed choice instead of simply accepting a setting because it happens to be the default.

Troubleshooting with AI

Perhaps the most useful part of these conversations wasn't getting an answer to any one question. It was being able to troubleshoot a series of related problems.

I could show ChatGPT a screenshot of my Blogger or DNS settings and ask whether something looked correct. When a status changed from "failed" to "unknown," I could ask what that meant. When the site started working but Facebook wasn't finding the right image, we could move on to that issue. When Feedly raised new questions, I could ask about RSS settings.

In other words, I didn't have to know the correct terminology before asking for help.

That's particularly valuable with a project like this because one problem can involve several different systems:

• Blogger controls the blog and its feed.

• The domain registrar manages the DNS records.

• HTTPS depends on the domain being configured correctly.

• Feedly reads information supplied through the RSS or Atom feed.

• Facebook and other social networks retrieve information from the webpage to create link previews.

When something doesn't work, determining which system is causing the problem can be more difficult than fixing the problem itself.

ChatGPT has helped me sort through those layers.

Still Learning

Moving Heartland Genealogy to Blogger has turned into a much larger learning experience than I anticipated.

I've learned that moving a blog isn't simply a matter of copying posts from one platform to another. A blog is connected to a much larger ecosystem—domains, DNS servers, RSS readers, image hosts, social networks and search engines.

I've also learned not to panic when a setting says "failed," an image doesn't appear where I expect it, or a DNS change doesn't seem to work immediately. Sometimes the answer is to correct a setting. Sometimes it's to understand how two services interact.

And sometimes the answer really is:

Wait 30 minutes and check again.

Fortunately, I've had an AI troubleshooting partner willing to answer all of those "What does this mean?" and "Is this correct?" questions along the way.

My move to Blogger may not have gone exactly as I originally envisioned, but I'm coming out of it knowing a lot more about how my blog actually works.