PMS

In-house software & AI. Toronto + Tampa, since 2009. We build web, mobile, cloud, and private LLMs — no offshore.

[PMS @PositionMySite]

@The_Muhib Checkout first if analytics shows drop-off there, since that's lost money already in the cart. Otherwise page speed on mobile product pages, and it's usually the photos: oversized JPEGs straight from a phone. Converting them to WebP is often the fastest win of the hour.

[PMS @PositionMySite]

@alexwolk1 Agree on merging lookalikes. The quick way to find them: sort pages by word count and GSC impressions, then group near-identical service/location pages. Those are usually the ones Google won't index. How we find thin pages: https://t.co/KbNYZyDLEI

[PMS @PositionMySite]

@Enhale11 Nice turnaround. For the last 2, run URL Inspection and compare the user-declared vs Google-selected canonical. After a domain move, Google often still picks the old URL or a near-duplicate. Canonical check: https://t.co/2EDNJLgYz8

[PMS @PositionMySite]

@JustMadushan We'd add: crawl the old URLs a few months in and check every one still lands in a single 301. Redirect chains from later http/www/slug changes are a common reason moved pages stall. Quick hop check: https://t.co/4yXubXNIjE

[PMS @PositionMySite]

@SHKImran2705 Glad it helps, Imran. Shout if Search Console shows anything odd once it's fixed.

[PMS @PositionMySite]

@dokoiku_tokyo 試してみてください。予約クリックのイベントが正しく取れていれば、どのページとデバイスで予約につながっているかがはっきり見えるはずです。

[PMS @PositionMySite]

If someone on your team retypes supplier invoices into the accounting system, that's the first workflow to automate. Read the fields, check them against the PO, flag only the mismatches for a person.

https://t.co/Mq9qfQ5VrU

#Automation #PositionMySite

[PMS @PositionMySite]

The same HR and ops questions get asked every week, and the answers already sit in your policy manual and SOPs. An internal assistant that answers from those documents and cites the page is far easier to trust than a generic chatbot.

https://t.co/URpfv3tOpo

#AI #PositionMySite

[PMS @PositionMySite]

Deleted products, renamed pages, old campaign links: they all still get clicks. A bare 404 loses that visitor. A real 404 page with search and your top links keeps them, and it should still return a 404 status, not a 200.

Check yours: https://t.co/aFkIe0ZmMe

#WebDesign #PositionMySite

[PMS @PositionMySite]

After a redesign, old URLs often go old > http > www > new. Each hop adds a round trip and gives Google one more chance to stop following. Point every old URL straight at its final page.

See how many hops a URL takes: https://t.co/uSugPpGzlX

#TechnicalSEO #PositionMySite

[PMS @PositionMySite]

@asaio87 A few hours is too soon. Check URL Inspection for canonical/robots issues, submit the sitemap, and if it stays excluded, add unique value. Guide: https://t.co/cLqfYDZbZD

[PMS @PositionMySite]

@AlexLielacher The useful part is the topics list. If ChatGPT cites you for topics you don't sell, that's a content gap to fix on your own site, not just a dashboard to watch. Pairing it with Search Console queries should show where the two disagree.

[PMS @PositionMySite]

@ThamiBenjelloun Classic free-tool effect. Worth checking that the generator page links clearly into warmup, since 5k clicks with no internal path to the money page is traffic that just leaves. A short "why your emails land in spam" block on the tool page tends to convert better than a banner.

[PMS @PositionMySite]

Good answer from him. Before noindexing anything, compare the stuck URLs with the ones that did index: near-duplicate templates, thin tag or filter pages and weak internal links usually explain the split. Improve or merge those first. We wrote up how to find thin pages: https://t.co/DFs7koo0TI

[PMS @PositionMySite]

@BaskaranReshma Matches what we see. Gemini leans on Google's index, so if those posts aren't indexed in Google, it won't cite them however often ChatGPT does. Run the cited URLs through URL Inspection in Search Console first. We wrote up how to check this free: https://t.co/cLqfYDYEa5

[PMS @PositionMySite]

@HunterLapeyre Agreed. They're decent at drafting and weak at verifying. We treat agent output as a first pass and still check the boring stuff by hand: canonicals, stray noindex tags, internal links that actually resolve. That's where the errors hide.

[PMS @PositionMySite]

Two more that catch most surprises: the "Why pages aren't indexed" reasons in the Pages report (a sudden jump in noindex or redirect usually means a deploy changed something), and the Core Web Vitals mobile report for any URL group flipping to Poor. Then a quick look at top pages' clicks vs last week.

[PMS @PositionMySite]

@andyliang17335 Good foundation. Next number worth watching: how many of those 71 sit within 3 clicks of the homepage. Deep pages with no internal links tend to stay indexed but rarely show up. How we check click depth: https://t.co/eTvKvHrECR