View source for own your links

{{stub}}

'''<dfn>Own your links</dfn>''' is the concept of creating links on your own website that redirect to other properties you own, for instance social media accounts or content you have created on other websites.

== Why ==
By owning a link, you can change its destination as appropriate without having to rely on the owner of the site to which a link points setting up redirects if the link destination changes.

This may be useful if you change your profile name on a social media service. If someone takes your old profile name and you always link directly to your profile, people may not find the content to which you were linking when you first created the link.

Google site-specific searches with your site, will show content from sites you have setup such redirects for!

== How to ==

To "own" a link, you should:

* Come up with the name for your link and identify where it is going to point.
** (i.e. example.com/github/ could point to github.com/<yourprofilename>)
* Create a redirect on your site that points the name of your link to the destination.
* Use your link when referring to the resource to which your link points.

For instance, Alice may create a page on her site with the URL example.com/twitter/. Alice uses this URL to link to her Twitter account rather than her main Twitter URL.

* You may want to use a <samp>&lt;meta&gt;</samp> tag with <code>HTTP-Equiv</code> as part of a 302 Redirection ([https://indieweb.org/meta_http-equiv_status meta http-equiv status]), however this is limited to a specific URL. See below for how to redirect all URLs that start with a particular path.

=== How to generically ===
For [[silos]] with deep links like GitHub and Twitter, it's better to use the name of the silo as your path, because the rest of the path is highly dependent on the silo.

For some [[silos]] with shallow or generic paths, you can use a generic name instead for redirecting.

For example, wiki silos often treat (most) paths a generic flat list of names of pages, thus for those you can use <kbd>/w/</kbd> or <kbd>/wiki/</kbd> or <kbd>/topic/</kbd> as your redirect path.
* E.g. see below examples, {{t}} uses <samp>/w/</samp> to redirect wiki pages to the [[PBWorks]] silo.

=== How to Apache htaccess ===
If you use [[Apache]] with [https://httpd.apache.org/docs/current/mod/mod_alias.html mod_alias] enabled and can access your .htaccess file, you can add an instruction like

<code><nowiki>RedirectTemp /github https://github.com/yourGHusername</nowiki></code>

replacing "yourGHusername" with your GitHub username.

=== How to nginx config ===

You can use the following [[nginx]] config to own a link:

<pre><nowiki>
location ~ ^/github/(.*) {
     return 307 https://github.com/yourGHusername/$1;
}
</nowiki></pre>

replacing "yourGHusername" with your GitHub username.


{{jacky}} uses a "one liner" approach as follows (within a <code>server</code> block)

<pre>
rewrite ^(/github)(.*) https://github.com/jalcine$2 redirect;
</pre>

== IndieWeb Examples ==
=== Tantek ===
{{t}} owns his links for:
* PBWorks homepage & individual pages [http://tantek.com/2010/264/t1/activitystreams-object-type-filter-falcon-feed since at least 2010-09-21] with tantek.com, and [http://tantek.com/2010/205/t2/short-url-thoughts-design-whistle since 2010-07-24] with his shortdomain ttk.me.
** https://tantek.com/w/
** https://tantek.com/w/Markdown
* GitHub profile & repos [https://indieweb.org/wiki/index.php?title=User%3ATantek.com&type=revision&diff=21020&oldid=20000 since at least 2015-07-23]
** e.g. https://tantek.com/github/cassis
** related post: https://tantek.com/2021/084/t1/ownyourlinks-indieweb-github-redirect 
** more details and future thoughts: [[User:Tantek.com#GitHub]]
Both of which show up in Google site-scoped searches as if they’re on his domain! E.g. 
* [https://www.google.com/search?q=site%3Atantek.com+%22tantek.com%2Fgithub%2Fcassis%22 Google search for site:tantek.com "tantek.com/github/cassis"] (first result is content from Github.com and third result is content from PBWorks, shown in results as if they are on tantek.com)

=== James ===
* {{capjamesg}} owns his Twitter and Instagram links as of May 2022:
** https://jamesg.blog/github/
** https://jamesg.blog/instagram/

=== Matthias ===
{{pfefferle}} owns his links for:

* Twitter since around 2019:
** https://notiz.blog/@ redirects to https://twitter.com/pfefferle
* I wrote/use a little WordPress Plugin, to also own tweets/toots and code (github.com, gitlab.com, ...): https://github.com/pfefferle/wordpress-ownyourlinks

=== Jacky Alcine ===
{{jacky}} owns his links [https://jacky.wtf/2022/7/sIWP since 2022-07-27] for silo path redirects for /twitter and /github:
* "Small QoL change to my site (on a proxy level): I've added support for "owning" my own URLs. So /twitter/status/1545916088956903424 properly redirects to Twitter and /github/sqlite-hypercore goes to the right place. Long-term goal is to retroactively update links on my site that point to myself to point to my site first so, later down the line, I can actually serve it from my site (and go to the silo if needed)." July 27, 2022

=== Add yourself! ===
* {{addyourself}}

== Other Examples ==
* URL shortener software https://yourls.org uses a redirect for github releases
** https://yourls.org/download redirects to https://github.com/YOURLS/YOURLS/releases as of 2022-05-25

[[Category:OwnYour]]

== See Also ==
* [[permalinks]]
* [[own your data]]
* [[URL shortener]]
* [https://buttondown.email/ownyourweb/archive/issue-10/ Own Your Web – Issue 10: Links Worth Sharing]