Instagram Post Sorter Supported Pages
Decide whether an Instagram URL is a locally verified INS Sorter profile-grid target, an unsupported route, or a surface without publication readback.
On This Page
The only locally verified SKU10 target is a canonical one-segment Instagram profile grid, such as instagram.com/example/. Home, Explore, Direct, a single post, Reels routes, Stories, settings, challenge pages, and other nested paths are outside the current runtime contract. Broader page coverage claimed by another sorter does not expand INS Sorter's scope.
Support requires three checks
- Eligible route: the pathname contains exactly one valid username segment and is not a reserved route.
- Ready page evidence: the page has a main region and recognizable post/reel cards; an empty grid is different from a missing grid.
- Current-session access: the browser can already display the profile. INS Sorter does not bypass login, challenge, privacy, or permissions.
Only after all three checks should the runtime move from checking to ready.
Route, field, and stop matrix
This matrix is stricter than “works everywhere.” A canonical profile with no posts can pass the route check and return an explainable empty-grid state. An unsupported page fails before it can become a valid grid target.
State dictionary
There is no “probably supported, keep trying” state. Competitor listings can document market language, not SKU10 capability.
Exact route rules
After decoding, the pathname must have exactly one segment containing 1–30 word/dot characters. Reserved routes include accounts, about, api, challenge, developer, direct, directory, emails, explore, legal, p, privacy, reel, reels, stories, terms, and web.
The page must also expose cards under main; links inside dialogs do not count as profile-grid candidates. A valid route can still be not ready while Instagram is loading.
Five pre-run checks
- Read only the URL pathname and confirm
/username/shape. - Exclude Home, Explore, Direct, single-post, Reels, Story, settings, and nested paths.
- Confirm Instagram itself is visible in the current session without bypassing access controls.
- Wait for the profile grid, then expect
checking → ready; distinguish empty from missing grid. - Choose field, direction, and loading boundary only after
ready; otherwise stop with a non-sensitive state record.
Limits
The researched competitor pages claim profiles plus various Reels, Explore, hashtag, search, location, saved, tagged, repost, or feed surfaces. Those are vendor-specific claims alongside vendor exports, analytics, and other architectures. They do not apply to SKU10.
Even on a supported profile, INS Sorter covers only the current loaded set. Fields can be missing, All does not guarantee complete history, and route navigation clears old profile evidence. It does not modify the public grid, access unknown metrics, export a report, or monitor continuously.
Run only on an eligible page
When route and page evidence both pass, start from the INS Sorter product page. If they fail, stop; this page does not use an install CTA for Reels, Explore, single-post, or public-grid-reordering intent. Troubleshooting siblings are not public, so no placeholder links are present.
Frequently asked questions
Is /username/reels/ a supported profile page?
No. It has two pathname segments and is outside the current one-segment profile-root contract.
What is the difference between an empty and unsupported page?
A canonical profile can pass route checks but contain zero candidate cards. An unsupported route is rejected before valid grid scanning.
A competitor supports Explore. Does INS Sorter?
No. A competitor claim proves only that vendor's declared scope.
Can it work with private profiles?
Only current-session page evidence is considered; INS Sorter does not bypass privacy, login, or challenge boundaries.
Does sorting change the grid visitors see?
No. It temporarily reorders loaded cards in the current browser tab.
Sources
- Insta Sorter Chrome Web Store listing: broad vendor page list plus a loaded-content limitation; not SKU10 evidence.
- InstantDM Feed Sort: vendor claims for Posts/Reels and current-session access, mixed with exports and unrelated marketing.
- Sort Feed Instagram sorter guide: supported-page and visible-session language for another product.
One-segment route parsing, reserved routes, main/grid evidence, and empty/missing states were checked against SKU10 local source on August 31, 2026. No login, real-account collection, deployment, publication, or production readback was performed.