@kanejamison

46 Followers
117 Following
47 Posts

Founder of @ContentHarmony. We help SEOs & content marketers build amazing content briefs and optimize their content - in half the time you used to spend.

Still making content with our team at Fixture.media.

Content Harmonyhttps://www.contentharmony.com
KaneJamison.comhttps://www.kanejamison.com

Biggest problem with GPT is how to get it to quick making shit up like a drunk guy at a bar.

Getting some amazing "truthy" insights from it that are useful regardless, but it's making up citations and things that make the statement technically inaccurate.

Big class="lead" vibes on this featured snippet.
Sometimes SaaS support is just helping your customers with their end goal, not with your software.
This has been quite a successful misinformation campaign on the part of groundhog.org.
Everybody wants to be an entrepreneur, but don't nobody want to gather 48 additional documents to get a mortgage pre-approval.

I'm sort of excited for Bing to have access to GPT-3 powered results.

But I’m *really* excited that maybe they'll use it to stop sending me these emails.

#seo

@wilreynolds I was chatting with a teammate today about client communication and meetings and the follow up from the conversation was basically having them read everything ranking for “communicating with clients site:seerinteractive.com”.

Sharing since I thought you'd appreciate it. It's quite a resource when you line them all up like that.

I would not be surprised to see an "AI Content Rider" or sections that clearly state "vendor will disclose all usage of AI-based content creation, including but not limited to GPT-3 and tools that use GPT-3. Vendor will require all subcontractors to sign this policy as well."

"What would a contract requirement even look like?"

Actually pretty easy - most agency contracts have sub-contractor requirements as well as 'original content' types of clauses already.

Here's a simple example but they're often more specific than this.

I recently drafted up an internal AI policy to clarify for our team how we're using it.

TLDR - you're encouraged to use GPT-3 for any operational improvements - but do not use it for generating published content, and disclose its usage anytime it ends up in a deliverable.